Mutant_Tractor
Enthusiast
Enthusiast

vRealize Orchestrator 6.0.3 with VCSA 6.0 U1a

Jump to solution

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:

Re: Installing vRO v6.01 but not showing in web client

Can run workflows, auth using the client, everything, just no plugin in web client.

com.vmware.vco isn'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.

This is driving me crazy, does anyone know of anything relating to this behavior?

Myles

1 Solution

Accepted Solutions
Mutant_Tractor
Enthusiast
Enthusiast

Worked it out:

http://orchestration.io/2015/09/28/deploying-vrealize-orchestrator-6-0-3/

When running the register extension to vCenter workflow, I was only specifying vro1.lab.mylesgray.io, not: https://vro1.lab.mylesgray.io:8281 as it should have been.

It also fails when setting up with the Configuration Manager, so I assume it just specifies the FQDN also, and not the protocol + port.

View solution in original post

1 Reply
Mutant_Tractor
Enthusiast
Enthusiast

Worked it out:

http://orchestration.io/2015/09/28/deploying-vrealize-orchestrator-6-0-3/

When running the register extension to vCenter workflow, I was only specifying vro1.lab.mylesgray.io, not: https://vro1.lab.mylesgray.io:8281 as it should have been.

It also fails when setting up with the Configuration Manager, so I assume it just specifies the FQDN also, and not the protocol + port.