"Unable to get deployment status" - fresh install VCSA 7.0.3.01400

[jaguardin]

Has anyone come across this?

First I was not able to get past stage 1 with 7.0.3.0700

So I deleted that VCSA, tried with the latest version and I'm getting this error. I've tried multiple suggestions online that I found + forum.

If I reboot the VCSA, I can no longer hit the vCenter page either. I have to start services manually.

Please help if you have any suggestions! Thanks.

[a_p_]

In most cases such issues are caused by missing DNS records.
Make sure that you have working forward (Host-A) and reverse (PTR) records.

To test this, run e.g. nslookup <vCSA-IP-Address> <DNS-Server-IP-Address> to ensure that the vCSA's IP address resolves to its FQDN.

André

[sombrafam]

I have the PTR records in my DNS and I still get the errors. So I think it's something else.

user@rotom:~/SharedImages/vc-vcenter-vm.segmaas.1ss-2023-12-15--02.56-28917$ nslookup 10.230.63.10 10.230.56.2
10.63.230.10.in-addr.arpa name = vcenter-vm.heatmor.
10.63.230.10.in-addr.arpa name = vcenter-vm.segmaas.1ss.

user@rotom:~/SharedImages/vc-vcenter-vm.segmaas.1ss-2023-12-15--02.56-28917$

[Kinnison]

Hello,

And which of the two "PTR" records corresponds to the FQDN name of your "vCenter" object.

Regards,
Ferdinando

[sombrafam]

vcenter-vm.segmaas.1ss

[Kinnison]

Hello,

So, what is the purpose of having two PTR records that point to two different "FQDN" names for the same IP address?
As other have already told you, you need to make sure that: "the vCSA's IP address resolves to its FQDN", so why don't you start removing the one PTR record that is not relevant to the purpose. Apart from this, the LOGs can provide further clues about the causes of the failed deployment, you should consult them.

Regards,
Ferdinando