I am attempting to instantiate a vApp from a catalog using Orchestrators built in "Instantiate a vApp template" workflow, and it is failing with the error "The VCD entity network "9902007_SERVERS_VLAN1171_Webserver Test" specified for VM "Webserver Test" does not exist"
Looking at the script, it does not appear to be taking any info for the "NetworkSection".
Has anybody run into this before? If so, how did you fix it?
Looks like this was caused due to an Org Network being added to the vApp that was then carried over to the vApp template.
Not wanting to re-invent the wheel, has anybody created a workflow that strips a vApp of org networks while capturing a vApp to a vApp template?
Your question was asked internally here... my most recent reply was as follows:
hold on a sec... I just tested and was unable to duplicate...
In one organization, I created a new vApp with a vm in it. I connected that vm to an Org Network (MySpecialOrgNetwork) in that Org. I then powered it up and made sure the vApp was good.
Next, I shutdown the vApp and captured it to a public catalog.
I wrote a simple workflow that takes a CatalogItem as an input so that I could select the CatalogItem from that public catalog. The workflow then converts the catalog item into a vAppTemplate object. I store that object as an attribute within my test workflow and the next embedded workflow I call is the Library copy of the Instantiate a vApp Template. I synchronized presentation and cleaned up the attributes.
Finally, I tested:
Upon running the workflow from Org B, I selected the CatalogItem (vAppTemplate in Org A's Publicly shared catalog) from OrgB's Catalog (Orgs can see Public vAppTemplates from other Orgs only as CatalogItems - not as vAppTemplates within their own Org). I then selected the VDC in Org B and deployed. The result was a vApp with a vm connected to vAppNet-MySpecialOrgNetwork. No errors on instantiation...
So, with that - what version is your vCloud Director install? Mine is 1.5.1 and I get the results described above.
I don't have time to test your thought, but my first instinct is that there may be troubles with this approach...
You could probably setup a blocking task that prevents the vApp Template from being created while it sill has an org network attached... but, since the state of the vApp is in flux, you probably wouldn't be able to modify it via the api (ie: workflow). Based on my testing as noted in my other reply here, this shouldn't actually be an issue though as Instantiating a vAppTemplate that has an Org Network connection that doesn't existin in the target Org results in the vms being connected to a vAppNet-<originalOrgNetworkName> vApp Network.
That 'may' be the issue then.. please let us know if the upgrade results in the behavior that I posted from my experience
I'm unsure why this is happening to you... it would be best to continue this issue with GSS.