1 person found this helpful
Sort of... We do not get any errors like this so that is a little different.
We do a similar thing, we have a "catalog" org, and our many orgs link to the same external network (in many cases) but vCloud treats each orgs networks as different.
We named our orgs networks the same to make it a little more clear, but at deploy in the gui users need to pick the network.
If using the API to deploy (like we are in most cases) you can look at the template network configure to get the network name, and do a rewire at instantiate by finding the org network with the same name. Using the same name made the matching easier.
Thanks cfor for the hint with the API.
Unfortunately we do not use the API. Our vCD is kind of a self-service platform for all engineers (about 100) in our company, so the API is not a solution for us.
I have an update on this from VMWare support:
Seems that a fix for this will be included in next patch 5.1.3 and also in vCD 5.5.
Is partially the same issue like one of my colleagues had in another thread: