Provide information on how to resolve vSphere HA agent problems due to third-party VIBs.
Symptoms:
- Unable to install or update the vCenter Server vSphere High Availability (vSphere HA) agent service.
- Powering on virtual machines fails with error:
The host is reporting errors in its attempts to provide vSphere HA support
- In the VMware vCenter Server summary, you may see this vSphere HA service error:
vSphere HA agent for this host has an error: vSphere HA agent cannot be correctly installed or configured
- Manually removing the FDM agent by running the esxcli software vib remove -n vmware-fdm command may fail with an error similar to:
[DependencyError]
VIB Acronis_bootbank_active_drive_1.0-28 violates extensibility rule checks: [u'(line 48: col 0) Element vib failed to validate content']
Please refer to the log file for more details.
Note: that the exact name of the third-party VIB may differ from these messages.
- In the /var/run/log/esxupdate.log file, you see entries similar to:
bootbank_qlogic_hcli_2.2.60.7.0.0vmw.500.0.0.472560 violates extensibility rule: Installing the VIB
fdm-installer: [24683] 2013-07-18 18:41:45: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: [DependencyError]
fdm-installer: VIB QLogic_bootbank_qlogic_hcli_2.2.60.7.0.0vmw.500.0.0.472560 violates extensibility rule checks: [u'(line 31: col 0) Element vib failed to validate content']
fdm-installer: Please refer to the log file for more details.