Check compliance on a cluster with base image with custom addon fails with "An error occurred while connecting to depot."
search cancel

Check compliance on a cluster with base image with custom addon fails with "An error occurred while connecting to depot."

book

Article ID: 381221

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vCenter Server

Issue/Introduction

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...

Resolution

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

This can be tested using a wget from the host to the URL in the error in the log for the specific environment. 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 

Ensure this is not a match of "Download failed: <urlopen error timed out>", Enabling vSphere HA and vLCM Compliance check fails after upgrading vCenter Server to 8.0 U3 as this has a different cause and resolution.