Hi everyone, i have new deploy VM Orchestrator on vCenter Server.
When i finished deploy VM vRO on vCenter, i check nslookup FQDN on VM vRO using root account,it normal but i try to login in to web client using IP or FQDN for vRO it can't connect to service or login in to vRO.
I already create record A and PTR on DNS server using windows server 2012 R2. On DNS server can resolve record and FQDN for vRO.
Who used to deploy VM vRO 8.4 please help me to solve this issues. Thanks you very much.
I have no idea what Khong the truy cap trang web nay means. But I also see CONNECTION_REFUSED
You may have some kind of firewall between your client and server, or the vro services are not running?
One way is to open the web console of the vRO VM and check if you see something like this
This content shows that all services are started and the application is ready. If this is not the case then you'll need to either
- Hit the VAMI interface (not sure if 8.x uses it?)
- Or SSH to the VM and check the status of the pods. Theres's a KB here - https://kb.vmware.com/s/article/76870 - which has the commands you need to display status output & some info on how to resolve if you're in this position (which you might be...?)
The "Welcome to" message on the console simply means that the VM has booted, many services attempt to start after that. So having the Welcome there does not mean all services are running.
vRA/vRO 8 appliances do not have a VAMI anymore.
Make an SSH connection to 10.10.200.26 and log in as root.
Then type kubectl -n prelude get pods
You may check the output or post it here.
ah, I've seen this before. It was quite annoying - same as you fresh install, but couldn't actually use it - No way to log in.
I found similar mention in some release notes (8.1 maybe? with a possible fix), and also this kb article - New installs of vRealize Orchestrator 8.x fail to install due to a POD STATUS of 'CrashLoopBackOff' ...
Hopefully that link will work for you, otherwise you'll be in the same boat we were in - Our solution ended up being installing a newer vRO version (8.6.2 we ended up going with as any earlier version reaches end of general support by October!) - I believe the current latest is 8.8.
TLDR; try that link above if applicable, or install a newer vRO (I'd recommend one that is not about to go out of general support >= 8.6.2)