vSphere HA agent for ESXi host has an error: vSphere HA agent cannot be installed or configured
Article ID: 381240
Updated On:
Products
Issue/Introduction
Symptoms:
- The following error messages are observed:
- "Cannot complete the configuration of the vSphere HA agent on the host."
- "Applying HA VIBs on the cluster encountered a failure."
This indicates that there may be issues with the vSphere HA agent configuration or the application of the HA VIBs on the cluster. The problem could be related to firewall rules, network connectivity, or ESXi host configuration.
Environment
VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.3
Cause
Task-Status.json for vCenter server:
-> There is a connection error with Depot.
On ESXI - /var/vmware/lifecycle/task-status.json
{"5291db0b-XXXX-XXXX-XXXX-4e8a3ca11b11": {"operation": "com.vmware.esx.settingsdaemon.software.scan", "status": "FAILED", "user": "root", "startTime": "[YYYY-MM-DDTHH:MM:SS]", "endTime": "[YYYY-MM-DDTHH:MM:SS]", "progress": {"completed": 0, "total": 100}, "error": {"id": "com.vmware.vcIntegrity.lifecycle.EsxImage.DepotConnectError", "message": {"id": "com.vmware.vcIntegrity.lifecycle.EsxImage.DepotConnectError", "default_message": "An error occurred while connecting to depot.", "args": []}, "resolution": null, "time": "[YYYY-MM-DDTHH:MM:SS]"}}}
ESXi: lifecycle.log
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: imagemanagerctl:1171 INFO Calling with arguments: software --scan --software-spec /var/run/lifecycle.scan.swspec --depot http://VC:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__vmw-ESXi-8.0.3-metadata__index__.xml --depot
http://VC:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-19__index__.xml --task-id 52f43aa4-ca7d-f8b6-5dc3-55b0fef71018
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 52935073-57ba-9db3-2eeb-001003fde660
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 5288b719-d173-550b-27f9-37e0e6cc8ed9
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 524e087e-3d02-d2ba-3211-34c794e9cf38
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 52004a44-91bc-ab7c-a4cb-b83b56153712
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 52fd277d-034f-010c-dfc5-7b6de9552f11
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: task:328 INFO Cleaning up task: 52f43aa4-ca7d-f8b6-5dc3-55b0fef71018
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: imagemanagerctl:624 DEBUG Got spec from vAPI: {'add_on': None, 'base_image': {'version': '7.0.3-0.105.22348816'}, 'components': None, 'hardware_support': None, 'solutions': {'com.vmware.vsphere-ha': {'components': [{'component': 'vsphere-fdm'}], 'version': '7.0.3-24024786'}}}
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: HostImage:185 DEBUG Deferring initiating installers
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: HostImage:223 INFO Installers initiated are {'live': <vmware.esximage.Installer.LiveImageInstaller.LiveImageInstaller object at 0xe8f125c790>, 'boot': <vmware.esximage.Installer.BootBankInstaller.BootBankInstaller object at 0xe8f088e400>, 'locker': <vmware.esximage.Installer.LockerInstaller.LockerInstaller object at 0xe8f1247f70>}
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: DepotCollection:321 DEBUG Downloading depot index.xml from http://vc:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__vmw-ESXi-8.0.3-metadata__index__.xml
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:372 INFO Opening http://vc:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__vmw-ESXi-8.0.3-metadata__index__.xml for download
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 9 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 8 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 7 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 6 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 5 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 4 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 3 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 2 retry left...
[YYYY-MM-DDTHH:MM:SS] lifecycle: 4736221: Downloader:210 WARNING Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 1 retry left...
Resolution
The customer’s firewall team should allow ports 80, 9084, and 9087. In some cases, these ports may also need to be enabled on the ESXi host if they are disabled. Once the firewall is configured, communication will be restored, and HA will be reconfigured.
Feedback
