Hi All
We have set up a productive vCloud Director 5.1.2 environment which works quite good so far. We have one Organization called LIBRARY which contains all our template vApps in a published and shared catalog. Beside this we have a couple of Organizations for each department like Engineering.
Some of the template vApps in the catalog are configured with an internal network (172.20.20.x) which is connected to the external network "External V520 VMS-Net" with NAT option.
The issue is now the following:
If I want to create a vApp in Engineering by deploying the vApp template from the shared catalog in LIBRARY, it fails for vApps which have NAT configured with connection to the external network.
"Specified parent network External V520 VMS-Net (com.vmware.vcloud.entity.network.<ID>) is invalid. Either it is inaccessible in the VDC or it is not part of the correct organization".
All Orgs have the same external networks (they have the same names). But I assume that vCD does check the internal object ID (like com.vmware.vcloud.entity.network:ee4e320c-96cb-4b0d-8349-355881a19e12) instead of the name (like External V520 VMS-Net).
Screenshots are attached.
Anyone facing the same issue or having an idea how to work around this?
Thanks and regards
Christoph