Version 7.4.0.16380053
Resolver report:
A Require-Bundle could not be resolved. Resolver error data <Require-Bundle: com.springsource.org.apache.log4j; bundle-version="0.0.0">.
Caused by missing constraint in bundle <com.vmware.vco.vcoservice_7.4.0> constraint: <Require-Bundle: com.springsource.org.apache.log4j; bundle-version="0.0.0">
Version 7.4.0.13701555
Version 7.4.0.11197016
Version 7.4.0.7760491
Version 7.3.0.5751400
Version 7.3.0.5221408
Update procedure:
In Orchestrator appliance:
In Web Client appliance:
Dear support
Good morning.
Thanks a lot for the solution.
I tested in my lab environment and it worked with no issues.
For the time being I can see the plug-in under the vCenter web client (FLEX), but under the vCenter HTML5, I can't see it under the registered plugins.
Thx
Tasos
Unfortunately, I don't have a Windows installation of vSphere Web Client at hand, so the follwoing info may not be fully accurate.
Conceptually, the steps are the same. The equivalent of /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/ folder should be C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\. To restart the service, instead of service-control check if there is vmon-cli in folder C:\Program Files\VMware\vCenter Server\vmon
So we moved to VCSA 6.7 and following the instructions was able to get the vro plugin and use the context actions to launch orchestrator actions from vm, resource pool, folder, etc... to work. After reboots of the appliances we can still access the orchestrator plugin to see workflows, but the context action items from the vm, resource pool, folder, etc... is now missing. I have verified that the list of managed context actions is fully populated. Have you seen this before, and if so what is the way correct this?
I have seen the context items disappear from time to time. If I go in and add/modify one context item, they all re-appear in the context menu again on the next login.
Actually, there is a real issue with the latest Web Client release (and we have a PR opened to Web Client team about it). When the vRO plug-in calls the Web Client API to register its context menus, the API call might throw a NullPointerException, causing context menu registration to fail.
You can check if this is the case is Web Client main log file (vsphere_client_virgo.log). Fixing this issue will require a code change in Web Client (and possibly in vRO plug-in), so I doubt adding/removing context items will help.
Seeing this in a couple of my customer's vSphere environments, as well as our team lab. After upgrading PSCs and VCSA to 6.7 U2 (from U1), they now see this Orchestrator client-plugin continually trying to download.
Here's a screenshot: