vCenter 9.1 depot is inaccessible or has invalid contents error is generated from the Sync Updates action in vCenter Server 9.1
search cancel

vCenter 9.1 depot is inaccessible or has invalid contents error is generated from the Sync Updates action in vCenter Server 9.1

book

Article ID: 441598

calendar_today

Updated On:

Products

VMware vCenter Server VCF Operations VMware vSphere ESXi

Issue/Introduction

  • SDDC Manager and vCenter have been upgraded to 9.1.0.0
  • To be upgraded next are the ESX hosts
  • When running "Sync Updates" on vSphere Lifecycle Manager - the error below is observed -

A general system error occurred: "A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot."  

  • The depot has been confirmed to be enabled and connected
  • The error below is seen in the vCenter log file - /var/log/vmware/vmware-updatemgr/vum-server/imageService.log -

YYYY-MM-DD hh:mm:ss,sss INFO imageService [xxxxxxxxxxxxxxx] [imageService xxx] Error parsing https://sddc_fqdn/vmware/vcf/umds/patch-store/hostupdate/vmw/metadata-210397.zip: ('Esxi: 9.1.0-0.25370933', 'baseimage', "Two base images share the same releaseID

  • When running an upgrade pre-check against a 9.0 workload domain where the vCenter has already been upgraded but the hosts have not, the Create and Commit draft check fails with the following error:

    Failed to invoke create and commit the desired state image spec

Environment

  • VCF 9.1
  • vCenter Server 9.1
  • vSphere ESX 9.0

Cause

  • Two base images share the same release ID
  • This can happen if the 9.1 image is created when the vCenter is still running 9.0

Resolution

If this issue is encountered, open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Additional Information

Provide the following when contacting Broadcom support:

  • vCenter Server support bundle.
  • ESXi host support bundles for hosts that are failing to configure as transport nodes.
  • Text of any error messages seen in NSX GUI or command lines pertinent to the investigation.

Handling Log Bundles for offline review with Broadcom support: