vCenter HA mode shows "Appliance state is out of sync"
search cancel

vCenter HA mode shows "Appliance state is out of sync"

book

Article ID: 345266

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • vCenter HA mode shows "Appliance state is out of sync".
  • In VCHA logs, you will see similar entries

    2019-06-18T12:42:56.634-05:00 error vcha[16620] [Originator@6876 sub=ReplFacade-largeFrp] Sync failed: /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.41703/plugins/
    updatemanager-ui-war-6.1.0/META-INF/maven/com.vmware.vum.client/updatemanager-ui-war/pom.properties, event: 4
    2019-06-18T12:42:56.836-05:00 error vcha[16620] [Originator@6876 sub=RsyncRepl-largeFrp] Rsync failed, retcode: 11, error:
    --> VMware vCenter Server Appliance 6.7.0.30000
    -->
    --> Type: vCenter Server with an embedded Platform Services Controller
    -->
    --> rsync: change_dir "/etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.41703/plugins/updatemanager-ui-war-6.1.0/META-INF/maven/com.vmware.vum.client" failed: No such
     file or directory (2)
    --> rsync: mkdir "/etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.41703/plugins/updatemanager-ui-war-6.1.0/META-INF/maven/com.vmware.vum.client" failed: No such file
     or directory (2)
    --> rsync error: error in file IO (code 11) at main.c(664) [Receiver=3.1.3]
    -->
Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 6.7.x
VMware vCenter Server Appliance 6.7.x

Cause

The missing directory updatemanager-ui-war-6.1.0 is created temporarily by the H5 client and then deleted.

Resolution

This is a known issue affecting VMware vCenter Server 6.7. Currently, there is no resolution.
This issue is resolved in VMware vCenter Server 7.0 version.

Workaround:
To workaround this issue follow the below  manual steps 

   1.1 Remove the existing vCHA configuration. For details,refer to VMware documentation
   1.2 Remove the following symlinks under vCHA replication dir:
        /storage/service-state/vsphere-ui/cm-service-packages
    /storage/service-state/vsphere-ui/lookup-service-packages
    /storage/service-state/vsphere-ui/vc-packages

   1.3 Re-create vCHA configuration again. 
      - Configure vCenter HA Basic Option with the vSphere Web Client. Refer here
      - Configure vCenter HA Advanced Option with the vSphere Web Client: Refer here

Additional Information

Impact/Risks:
Requires reconfiguration of VCHA.