Hello all, I'm storing various vCenter configuration objects (datastores, networks, datacenters, etc.), some stored as single values and others as an array in a configuration element. I'm having a strange issue where sometimes the object value returns as a string "notfound". All values retrieved from multiple references in the same action/workflow either all work (VC object returned) or all return "notfound". Other non VC value types (string, number, etc.) are retrieved from the same config with no issue. There's no external events I'm aware of that triggers the lookup failures.
The behavior is not being captured in the log file, so I may need to turn up the logging level to see what's going on. The objects all belong to a single vCenter instance, and the vCenter service was up during all workflow execution runs. I'm running vCO 4.2.1 Windows version with patch from KB 2015178 applied and vSphere 5.0 U1 vCenter/hosts.
Anyone seen this before?
Yes, this is a known issues. A new update release of the vCenter plugin would be provide around mid of June. You can open a Support Request if you want to get the version earlier.
Thanks.
Yes, this is a known issues. A new update release of the vCenter plugin would be provide around mid of June. You can open a Support Request if you want to get the version earlier.
Thanks.
Hi guys, in the release notes of the new vcenter plugin apparently the bug fix is not listed. Can anyone confirm if this issue is still present or if it's fixed in 5.1.1 ?
Thanks
https://www.vmware.com/support/orchestrator/doc/vcenter-server-plugin-5011-release-notes.html
Tommaso
Hi Tommaso,
In the short time I had it running (it is not compatible with vCenter 4.1 for me) the update still displayed the problem you are describing for me.
In case you haven't found it yet, the "workaround" for me was to edit the config element but then close without saving and the "not found" elements would be back to normal. Sometimes I had to do this a few times before it worked though.
It isn't much of a fix, but I found that I only had to do it after the Orchestrator service has been restarted.
Hope that helps,
Dave
Yes, it should be fixed in 5.0.1.1 if you use vCenter Inventory service (recommended).
Hi Dave,
Yes, you are right. It looks like there is still issue for the cases when the VC Inventory Service is not used. However, the use of VC Inventory Service is the recommendion since vCenter 5.0 was released (meaning from vCO4.2 and the current vCO4.2.1). I think the issue when only Property Collector is used will be addressed as well. However, if you are on vCenter4.1, there is no any value to upgrade vCO4.1 to 4.2 version and even less value to ugrade the vCenter plugin to 5.x versions. All of the changes and improvements there are targeted towards vCenter 5.0 and the use of the Inventory Service.
Hope this is a helpful guideline and I will keep you updated when the issue with vCenter4.1 is also resolved in vCenter plugin 5.0.x version.
Thanks.
Thanks for the update!