Search the VMware Knowledge Base (KB)
View by Article ID

vCenter HA cluster fails when upgraded/patched to vCenter Server Appliance 6.5 U1 (2151548)

  • 1 Ratings

Purpose

The article helps you to:

  • Prevent vCenter HA cluster failure on upgrade/patch to vCenter Server Appliance 6.5 U1.
  • Recover from vCenter HA cluster failure after upgrading/patching to vCenter Server Appliance 6.5 U1.

Resolution

To prevent the issue:

If you are planning to upgrade/patch your environment:

  1. Upgrade/Patch the Deployed Node(ensure node to be patched is passive) to vCenter Server 6.5 U1.

    (Deployed Node is the vCenter Server Appliance VM that you deployed. Peer and Witness nodes are cloned from deployed node).

    Refer the url for upgrade/patching VCHA:

    https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.upgrade.doc/GUID-C27CD7DF-AB52-4A77-A6A6-A966498D5CA0.html


  2. Before reboot, modify /opt/vmware/etc/vami/vami_ovf_info.xml file content:

    <network ovf="unset"/>

    to


    <network ovf="unset" ovfeth0="false" ovfeth1="false"/>

  3. Reboot the VCSA VM using this command in the Guest VM:

    reboot

To recover from the issue:

If you have hit the issue after upgrading/patching to 65U1, follow the below steps:

  1. Modify /opt/vmware/etc/vami/vami_ovf_info.xml file the content

    <network ovf="unset"/>

    to

    <network ovf="unset" ovfeth0="false" ovfeth1="false"/>


  2. Modify /etc/hosts and /etc/hostname with correct hostname entries.

    Eg: before applying the patch/upgrade, /etc/hosts file on deployed node should look like below:

    # VAMI_EDIT_BEGIN
    # Generated by Studio VAMI service. Do not modify manually.
    127.0.0.1 localhost
    <VCSA IP address> <VCSA FQDN> <VCSA Hostname>
    # VAMI_EDIT_END


    After patch/upgrade, the entry should have changed to :

    # VAMI_EDIT_BEGIN
    # Generated by Studio VAMI service. Do not modify manually.

    127.0.0.1  localhost.localdom localhost

    # VAMI_EDIT_END


    Modify the content as it was before upgrading/patching:

    # VAMI_EDIT_BEGIN
    # Generated by Studio VAMI service. Do not modify manually.

    127.0.0.1 localhost

    <VCSA IP address> <VCSA FQDN> <VCSA Hostname>
    # VAMI_EDIT_END


    Similarly, change the /etc/hostname file.

  3. Reboot the VCSA VM using this command within the Guest VM:

    reboot

    Note:  If you see the issue on witness or passive node, please follow the same procedure to resolve the issue.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: