vSphere HA failed to enable on host without hostname and DNS configuration.
search cancel

vSphere HA failed to enable on host without hostname and DNS configuration.

book

Article ID: 406120

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • vSphere HA failed to enable with below error message.

Cannot complete the configuration of the vSphere HA agent on the host. "Applying HA VIBs on the cluster encountered a failure". Failed installing HA component on the host: host-id An error occurred while downloading depot metadata from http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/_micro-depot_vendor-vmw_metadata—33_index_.xml.

  • From ESXi host, following events are observed in /var/log/lifecycle.log 

YYYY-MM-DDTHH:MM:SSZ Er(11) lifecycle[######]: imagemanagerctl:90 vmware.esximage.Errors.DepotConnectError: ([MetadataDownloadError('http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-165__index__.xml', '', "Could not download from depot at http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-165__index__.xml, skipping (('http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-165__index__.xml', '', '<urlopen error [Errno -2] Name or service not known>'))"), MetadataDownloadError('http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-LVO__metadata-161__index__.xml', '', "Could not download from depot at http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-LVO__metadata-161__index__.xml, skipping (('http://<esxi-hostname>.com.cn:9084/vum/repository/hostupdate/__micro-depot__vendor-LVO__metadata-161__index__.xml', '', '<urlopen error [Errno -2] Name or service not known>'))")

Environment

  • VMware vCenter Server 8.x
  • VMware vCenter Server 7.x

Cause

Hostname and DNS aren't configured.

Resolution

Configure hostname and DNS at DCUI:

  1. Login to the DCUI console of the Host using the root credentials.
  2. Go to Configure Management Network.
  3. Then to the DNS Configuration and update the correct FQDN.
  4. And reboot the Host.

Additional Information

Other possible issue which can trigger this alert :