vmware / nsx-t-datacenter-ci-pipelines

CI pipelines for VMware NSX-T Datacenter
Other
71 stars 43 forks source link

no pipelines configured #38

Closed elgwhoppo closed 5 years ago

elgwhoppo commented 5 years ago

Hey All, I’ve gotten to the point where the containers have all the files downloaded appropriately and they are in the /home/concourse directory but when I navigate to the concourse URL and even log in with nsx/vmware on port 8080 I don’t see any plus sign in the top right hand corner. What steps can I take to troubleshoot my configuration? I have all the containers up and running and concourse appears to be working just fine but I just can’t see the NSX-T pipeline for my modified yml file. I’m guessing it has something to do with my config file, but I’m not sure where to start looking at that. Thanks for any help!

rbales79 commented 5 years ago

Did you create the /home/concourse folder and place your edited pipeline yml in it before running the docker command?

elgwhoppo commented 5 years ago

jclarke@ubuntu1804:/home/concourse$ ls -lah total 3.6G drwxr-xr-x 3 root root 4.0K Mar 31 16:22 . drwxr-xr-x 4 root root 4.0K Mar 14 20:04 .. -rw-r--r-- 1 root root 1.7K Mar 31 15:45 docker-compose.yml -rwxr-xr-x 1 root root 744 Mar 31 15:45 generate-keys.sh drwxr-xr-x 4 root root 4.0K Mar 15 04:13 keys -rw-r--r-- 1 root root 8.4K Mar 15 03:29 nsx_pipeline_config.yml -rw-r--r-- 1 root root 3.6G Mar 15 04:11 nsx-unified-appliance-2.2.0.0.0.8680778.ova -rw-r--r-- 1 root root 155 Mar 31 15:45 pipeline_config_internal.yml -rw-r--r-- 1 root root 35M Mar 15 03:46 VMware-ovftool-4.3.0-7948156-lin.x86_64.bundle jclarke@ubuntu1804:/home/concourse$

Yep, it's in there. This is the one that is modified with all the correct vCenter information.

elgwhoppo commented 5 years ago

image

This is what I'm seeing when I hit the page. I watched Niran's youtube video from october of last year, he logs in with user main and then can see the nsx-t-install pipeline.

NiranEC77 commented 5 years ago

I believe the pipeline hasn't registered, probably because of a parameter issue in the config file. Hijack the nsx-t-install container and try to run fly-reset

Dyanngg commented 5 years ago

Closing issue due to inactivity