No Data path to deployed container to VCH via vRA Blueprint

[wongnwo]

vchLogs.tar.gz

For bug reports, please include the information below:

VIC version: 1.1.1 -

Deployment details:

./vic-machine-darwin create --target eso-vra-vc01.eng.vmware.com --image-store 'w2_hsx_cmbu_vnx7600_02_vra12' --name rw-vic11-02 --user svc.r2@vsphere.local --password 'xxxxxxxxxx' --no-tlsverify --volume-store="w2_hsx_cmbu_vnx7600_02_vra12"/rw-vic11-02:default --volume-store="w2_hsx_cmbu_vnx7600_02_vra12"/rw-vic11-02:customVol01 --force --public-network dvPortGroup --compute-resource E2E --bridge-network dvPortGroup2-VIC

Steps to reproduce: vRA Blueprint with container: registry.hub.docker.com/kitematic/hello-world-nginx Created new container network in BP. Attach few screenshots of BP.

Request for BP to be deployed in VCH. Deployment succeeds. Click on data path

Actual behavior: Validation of URL to container does not load home page. Sign network path is broken. Expected behavior: Expected to load home html for container app. Logs:

Attached logs from VCH and Screenshots of BP. Please contact wongrobert@vmware.com or via slack on VMware. Glad to share details of internal env.

[stuclem]

@anchal-agrawal is this the same as https://github.com/vmware/vic/issues/3542? Should we add the same release note entry as I added for 1.1.1? Thanks!

[anchal-agrawal]

I don't know how #3542 and this issue are related. Regarding how VIC Engine works with vRA, I'd defer to @hickeng.

[stuclem]

Attempt at release note:

• vRealize Automation cannot create VCH blueprints that use bridge network. #6345
  (https://github.com/vmware/vic/issues/3542)
  vRealize Automation cannot create blueprints for VCHs that have either on-demand or existing bridge networks. If you deploy such blueprints, containers cannot be reached over the network. Only the default bridge network works in the VCH.

  Workaround: Use container networks instead of bridge networks in VCH blueprints.

@anchal-agrawal does this do it?

[anchal-agrawal]

@stuclem I don't have a complete understanding of the issue yet to say whether the bridge network is the problem.

[stuclem]

After discussion with @anchal-agrawal, we're removing this one from the RNs.