I was working with a customer using vRealize Life Cycle Manager v8.1 and deploying a new vRealize Operations Manager 8.1 deployment. During the install, which contained 3 nodes the deployment failed with the following error whilst working on the first node:

LCMVSPHERECONFIG1000072
Error Code: LCMVSPHERECONFIG1000072
IP address assignment check failed. Please check if the network details are correct and retry.
Exception occured while validating the Hostname and IP of vm : vrops01 of product : vrops. Failed to find a VA with name : ‘vrops01’, ip : ‘172.1.1.1’, hostname : ‘vrops01.terataki.net’.

Resolution

On checking the log we could see that the vROPS node was failing at the point where it gets renamed. On checking further vRLSCM uses the vami_set_hostname command, “host -W 15 -R 1 -T “ to set the hostname of the node. This essentially does a reverse DNS lookup on the IP and uses the returned entry to set the hostname. In this case the customer did not have the PTR records and therefore the deployment was failing.

On creating the correct PTR records and verifying we were able to resolve them, we could then retry the failed request in vRSLCM. In our case we had to set the option to Delete VM=True in order to redeploy the failed node. The deployment was then able to succeed.

Further notes

It was found that the pre-check report run before the vROPS deployment was started showed that this was a potential issue that should have been resolved before proceeding.