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