Spent longer than necessary messing with vRealize Orchestrator and trying to get it to display the plugin in vCenter server appliance 6.0 U1, you can review my trials and tribulations here:
I have been trying to deploy vRealize Orchestrator 6.0.3 with my VCSA 6.0 U1 instance (supported according to compatibility matrix), the symptoms are almost exactly the same as this post:
Can run workflows, auth using the client, everything, just no plugin in web client.
com.vmware.vcoisn’t showing at all in the MOB browser however.
I have tried cat-ing the virgo.log file on the VCSA but nothing relating to vco-plugin comes up when I tell vro to register the extension with vcenter.
All that shows in the web client is the getting started page, nothing else – i have tried restarting the web client service and the appliance, also rebooting the vro appliance – nothing works.
As you can see, even OOTB config is broken for this release.
I stumbled across this article:
And, of course, I was stumbling at the simplest of hurdles, when registering the appliance extension with vCenter and executing the workflow you are prompted for “External address to advertise this Orchestrator” – I was just putting in my
FQDN, apparently, this is not how we do.
vro1.lab.mylesgray.io I needed to put in
Re-registered and BAM, working right off the bat!
Thanks to Chris Greene (@orchestrationio) for documenting this better than VMware.
Why not follow @mylesagray on Twitter for more like this!