VCHA cluster fails after upgrading/patching to VCSA 6.5 U1
search cancel

VCHA cluster fails after upgrading/patching to VCSA 6.5 U1

book

Article ID: 321242

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The article provides information on:

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


Symptoms:
After upgrading or patching the vCenter Server Appliance to 6.5 Update 1, you experience this symptom:

The VCHA cluster fails.

Environment

VMware vCenter Server Appliance 6.5.x

Resolution

To prevent the issue If you are planning to upgrade/patch your environment, perform these steps:
  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).

    For more information on Upgrading/Patching VCHA, see Patch a vCenter High Availability Environment.
  2. Before rebooting, open the /opt/vmware/etc/vami/vami_ovf_info.xml file using a text editor.
  3. Modify this line:

    <network ovf="unset">

    to

    <network ovf="unset" ovfeth0="false" ovfeth1="false">
     
  4. Save and Close the file.
  5. Reboot the VCSA  using this command in the Guest VM:

    reboot
To recover from the issue,If you have hit the issue after upgrading/patching to 6.5 U1, perform these steps:
  1. Open the /opt/vmware/etc/vami/vami_ovf_info.xml file using a text editor.
  2. Modify this line:

    <network ovf="unset">

    to

    <network ovf="unset" ovfeth0="false" ovfeth1="false">
     
  3. Save and Close the file.
  4. 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 address ip> <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 address ip> <vcsa fqdn> <vcsa hostname>
    # VAMI_EDIT_END

    Similarly, change the /etc/hostname file.
     
  5. Reboot the VCSA 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.


Additional Information

简体中文：升级/修补到 vCenter Server Appliance 6.5 U1 后，vCenter HA 群集发生故障

Powered by Wolken Software