After assigned the certificate to one of the esxi hosts. The host in the HA settings had a problem.
To fix the problem, disconnect the Host from the cluster once and reconnect. That did not fix the problem.
In the next step, we disabled and reactivated HA. This caused all hosts to get the following error:
1- Cannot complete the configuration of the vSphere HA agent on the host. "Applying HA VIBs on the cluster encountered a failure".
2- vSphere HA agent for this host has an error: vSphere HA agent cannot be installed or configured.
3- vSphere HA agent for this host has an error: The vSphere HA agent is not reachable from vCenter Server.
ESXi Version : 7.0b
Hi @yousefj86 ,
The only change was certificate replacement on one of the hosts, so suspecting this could be due to a certificate issue. Please try removing the host(one that got certificate replaced) and check if you are able to enable HA on the cluster with rest of the hosts.
If the issue is isolated to that particular host, then we can review /var/run/log/fdm.log for HA issues on it.
Hope that helps
Moderator: Moved to Availability: HA & FT Discussions
The following errors were found in one of the ESXi:
FDM Log:
- Error : Open of file /etc/opt/vmware/fdm/kvstore failed: No such file or directory
- Warning : Couldn't open kvstore
- Failed to retrieve port group config spec for 50 20 15 0c 66 41 0f 5b-a2 5c b1 0a ca 4c fb 1c caught exception Fault cause: vim.fault.NotFound
- Got error invoking retrieveDVPortgroupConfigSpec on vim.dvs.HostDistributedVirtualSwitchManager:ha-hostdvsmanager: N3Vim5Fault8NotFound9ExceptionE(Fault cause: vim.fault.NotFou
hostd Log :
- 2020-12-14T07:43:15.858Z error hostd[2771209] [Originator@6876 sub=Hostsvc.HostSpecTracker] AddDvsToHostSpec : object not found/hostspec disabled
vpxa log :
- 2020-12-13T13:28:20.312Z error vpxa[2770942] [Originator@6876 sub=hostdstats opID=269486a4-9c] Did not get any dvs entity metrics from the host
- 2020-12-13T14:13:09.395Z error vpxa[2770937] [Originator@6876 sub=PropertyCache opID=WFU-59fd500f update=227702] Failed to diff 50:datastore, had ManagedObjectReference[], got ManagedObjectReference[]
- 2020-12-14T06:54:22.574Z error vpxa[2770934] [Originator@6876 sub=PropertyCache opID=WFU-17ad4cc6 update=376624] Failed to diff 51:network, had ManagedObjectReference[], got ManagedObjectReference[]
Does anyone have an opinion on this? Does this information help?
Call support?