vSphere 6.5U1 was released on July 27th. This is an incremental update a lot of people wait for before upgrading from a previous version. I have been lucky to have been running on vSphere 6.5 for quite some time and have been enjoying it very much.
Obviously we never upgrade production first, if we can help it. I decided to attempt an upgrade on one of our QA vCenters that was deployed using the VCHA Advanced workflow. I followed my standard upgrade steps Updating a VCHA 6.5 vCenter however when I went to failover the Active node to the upgraded passive/witness nodes, services would not start, I then noticed that the hostnames had reset to localhost.localdom which is kind of a big issue as vCenter relies on the hostname being set.
I was able to workaround this issue temporarily by setting the hostname correctly in /etc/hostname and /etc/hosts to be able to recover from the failure and break VCHA. Luckily i had a snapshot to rollback to as well.
Now we had this one upgraded, I still could not re-enable VCHA. I went through the process to configure VCHA, however every time I would deploy the passive/witness it would still reset the hostname, and when I went to finalize the configuration it would fail because the passive/witness hostnames did not match the active node. It seemed the issue was not with the servers themselves but possibly with some updated scripts that sync certain configuration files.
I was able to find someone else who could reproduce this issue and we both opened a case with is being investigated by engineering.
Update. Finally heard back from support.
So it seems in some cases the VAMI configuration can be “corrupt” and can cause the hostname to reset.
After upgrading your appliance, if you see the hostname reset, you can run the following command to reconfigure it properly.
Once I used the configuration script to reconfigure the hostname I was successfully able to redeploy VCHA.