vSphere HA configuration fails with error “vSphere HA agent for this host has an error: vSphere HA agent cannot be installed or configured”

If you reconfigure on cluster level (disable/enable HA) OR host lever (Right Click on Host \ Select Reconfigure for vSphere HA), following event is seen.

The object 'Vim.Datastore.datastore-XXXX has already been deleted OR has not been completely created.

You may see following lines in VPXD.LOG.

2019-02-05T10:42:20.182-08:00 error vpxd[07320] [Originator@6876 sub=DAS opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea-01] EnableDAS failed on host [vim.HostSystem:host-2728,ils-cls1-esxi-02.coloils.local]: class Vmomi::Fault::ManagedObjectNotFound::Exception(vmodl.fault.ManagedObjectNotFound)
--> [context]zKq7AVMEAAAAAEklWwAjdnB4ZAAASi0fdm1hY29yZS5kbGwAAACHBgDesAYAtEECAd1KAHZtb21pLmRsbAABfioBAsVqPXZweGQuZXhlAAKXfT0CoAMjAvv6IgK/UUoC1xRNAj08SwJKnUsChJdLAl+pCwLB3wsCraQLAozACwIMiUsC/B0wA9FUBHZpbS10eXBlcy5kbGwAARfZBAIW9QwCX6kLAsHfCwKtpAsChswLAKtoGACceBgAiQsiBH9PAk1TVkNSMTIwLmRsbAAEJlECBdITAEtFUk5FTDMyLkRMTAAG9FQBbnRkbGwuZGxsAA==[/context]
2019-02-05T10:42:20.204-08:00 info vpxd[07320] [Originator@6876 sub=MoHost opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea-01] [HostMo::UpdateDasState] VC state for host host-2728 (uninitialized -> init error), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null)
2019-02-05T10:42:20.231-08:00 info vpxd[07320] [Originator@6876 sub=DAS opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea-01] [VpxdDasConfigLRO::Cleanup] Number of unprotected vms: 11
2019-02-05T10:42:20.231-08:00 info vpxd[07320] [Originator@6876 sub=vpxLro opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea-01] [VpxLRO] -- FINISH lro-53671774
2019-02-05T10:42:20.231-08:00 info vpxd[07320] [Originator@6876 sub=Default opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea-01] 
[VpxLRO] -- ERROR lro-53671774 -- -- DasConfig.ConfigureHost: vmodl.fault.ManagedObjectNotFound:
--> Result:
--> (vmodl.fault.ManagedObjectNotFound) {
--> faultCause = (vmodl.MethodFault) null, 
--> faultMessage = <unset>, 
--> obj = 'vim.Datastore:0c057a11-f239-452b-9ccc-113fd7f52161:datastore-3958'
--> msg = ""
--> }
--> Args:
--> 
2019-02-05T10:42:20.232-08:00 info vpxd[07320] [Originator@6876 sub=vpxLro opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea] [VpxLRO] -- FINISH task-135218
2019-02-05T10:42:20.232-08:00 info vpxd[07320] [Originator@6876 sub=Default opID=HostHAOpsActionCommand-applyOnMultiEntity-5316758-ngc:70749342-ea] 
[VpxLRO] -- ERROR task-135218 -- host-2728 -- vim.HostSystem.reconfigureDAS: vmodl.fault.ManagedObjectNotFound:
--> Result:
--> (vmodl.fault.ManagedObjectNotFound) {
--> faultCause = (vmodl.MethodFault) null, 
--> faultMessage = <unset>, 
--> obj = 'vim.Datastore:0c057a11-f239-452b-9ccc-113fd7f52161:datastore-3958'
--> msg = ""
--> }
--> Args:
-->

This problem may happen because of stale cache entries of data stores configured for heartbeat. To resolve this issue restart VPXD service on vCenter.

service-control --stop vpxd
service-control --start vpxd

Refer KB for more details on vCenter service stop/start.

Then reconfigure HA, if multiple host affected then disable/enable vSphere HA on cluster level, if single host is affected then reconfigure on host level (Right Click on Host select option Reconfigure for vSphere HA)

Advertisements

#datastore, #error, #vmware, #vsphereha