Error: An error occurred while connecting to depot.
search cancel

Error: An error occurred while connecting to depot.

book

Article ID: 381221

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vCenter Server

Issue/Introduction

  • Check compliance on a cluster with a base image and a custom add-on fails with
  • UI will show the error “a general system error occurred a depot is inaccessible or has invalid contents”
  • lifecycle.log from host

    lifecycle[2110183]: imagemanagerctl:358 Got spec from vAPI: {'add_on': {'name': 'x86ArmPartcomponentaddon', 'version': '1.0.0-1'}, 'base_image': {'version': '<ESXi version will be here>'}, 'components': {}, 'hardware_support': None, 'solutions': None}
    lifecycle[2110183]: Downloader:373 Opening http://<vCenter FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__vmw-<ESXi version will be here>-metadata__index__.xml for download
    lifecycle[2110183]: Downloader:210 Download failed: <urlopen error [Errno -2] Name or service not known>, 9 retry left...

  • HA status may be change to unintilized status after upgrading vCenter because HA agent vib can not be download.

Environment

7.0

8.0

Cause

DNS Resolution

Resolution

  1. Ensure the ESXi host can resolve DNS and reach vCenter over TCP 9084.

  2. This can be tested using a wget from the host to the URL in the error log for the specific environment. The ESXi version and VC URL will vary per environment. 
    wget http://<vCenter FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__vmw-<ESXi version>-metadata__index__.xml

  3. Check /etc/resolv.conf and /etc/hosts


Additional Information