Another cause for this is if the IP's assigned to the vRA VA exceed the column varchar length causing vRO initialization to fail (can happen with multiple IPv6 entries). You have this issue if the following apply:
- The vRealize Automation /var/log/vmware/vcac/catalina.out log shows an error similar to: Error Message I/O error on GET request for "https://<FQDN>:443/vco/api/status": Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out.
- The vRealize Automation /var/log/vmware/vco/integration-server.log shows an error similar to: [ApplicaitonEventHandler-1] ERROR {} [SqlExceptionHelper] Batch entry 0 insert into vmo_clustermember (contentversion, hostaddress, hostname, lastupdated, state, id) values (0, , '<LIST OF IPv6 AND IPv4 ADDRESSES>', 'localhost', 1464817655348, 1, '67e8c8ca-0150-4988-9d29-b7f844e04222') was aborted. Call getNextException to see the cause.
To work around this (in the case of DHCP):
- Edit the /etc/sysctl.conf and add the following to disable IPv6:
#disable ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
- Run 'sysctl -p' to reload the sysctl (ifconfig should show no IPv6 addresses)
- Run 'service vco-server restart' to restart vRO.
- Run the "Retry Failed' from the installation wizard to proceed.
Hope that helps!
