Comments on: Problem connection vCenter Orchestrator to vRealize Automation

By: Robert

Robert — Sat, 11 Apr 2015 11:09:33 +0000

Seems like a syntax validation problem within vRA. For some reason the IPv4 address you typed was interpreted as IPv6 address. The issue is discribed on Wikipedia pretty well: http://en.wikipedia.org/wiki/IPv6_address quote: “Colon (:) characters in IPv6 addresses may conflict with the established syntax of resource identifiers”

I’m not sure how the identification v4/v6 is done in vRA but I guess that’s what happend. Did you eventually, while typeing in the IPv4 address, at some point accidently type in a colon which you deleted later on? E.g. copy paste IPv4+Port into the “host” field? If so that could be the reason. Eventually the VMware dev decided it’d be a good idea to use colon characters in the address for identification of IPv6 adresses but forget to do a switch-back to IPv4 if the colon is deleted. If so, then that switch routine should be visible in the Javascript validation within vRA.

By: magander3

magander3 — Fri, 06 Feb 2015 13:23:20 +0000

Hi,
really don’t know and don’t have access to the environment now. The reason for using curl was just to verify connectivity from the vRA appliance and not create any permanent session. Adding /vco or /vco/api is not required in the vRA configuration.

thanks

By: Sean Pearce

Sean Pearce — Fri, 06 Feb 2015 11:37:59 +0000

What happens if you connect to both urls now, after the reboot? I note the curl example was a ‘permanent redirect’… What happens if you append /vco or /vco/api as per your original url?