This is an issue with the inventory service. You can tell vCO to NOT use the inventory service by adding the following line to vmo.properties, then restarting your vco-server service:
VMware is aware of the issue and will resolve it in a future release. Until then, you can use the vmo.properties setting as a work-around
Have you opened a support request for this ?
Well, if I disable the inventory service I can't even access vcenter:
- ch.dunes.util.DunesServerException: Could not initialize class com.vmware.vmo.plugin.vi4.VimPluginFactory
Which is bad
Then you definitely need to open an SR in case this is a known issue with a fix.
Yep, I did open an issue immediately after posting the thread here on the community.
Okay, I tried removing and readding one of my vcenters and either that, or the second restart of the vCO server, actually helped.
So now I am able to both access the vCenter inventory (whew) and the portgroupSpec contains the correct vlanId.
Thank you very much, Burke - that was a very quick response, impressive work
It seems that leveraging the inventory service has been the source of a lot of gaps like this one. You should be all set now.