Error: vCenter Sync Updates fails with "Two baseimages share the same releaseID" in imageservices.log

Products

• VMware vCenter Server

Issue/Introduction

When attempting to "Sync Updates" in vSphere Lifecycle Manager (vLCM), the task fails with: A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot.

The /var/log/vmware/vmware-updatemgr/vum-server/imageservice.log contains errors similar to: ERROR imageService ... [DepotMgr 51] Unable to connect to depot(s) ... ('ESXi:8.0.2-0.30.####', 'baseimage', "Two baseimages share the same releaseID: ESXi:8.0.2-0.30.####, but have different attributes: schemaVersion ('1.0' != '1.1')")

Environment

VMware vCenter Server

Cause

This issue occurs due to metadata corruption in the Lifecycle Manager database. Multiple base images share the same release ID but contain conflicting schemaVersion attributes, causing a validation failure during the depot synchronization process.

Resolution

Resolution: To resolve this issue, reset the VMware Update Manager (VUM) database to clear the corrupted metadata.

1. Take an offline snapshot of the vCenter Server Appliance.
2. SSH to the vCenter Server Appliance as root.
3. Stop the Update Manager service: service-control --stop vmware-updatemgr
4. Run the database reset utility: python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
5. Remove cached patch data: rm -rf /storage/updatemgr/patch-store/*
6. Start the Update Manager service: service-control --start vmware-updatemgr
7. Log out and back into the vSphere Client and initiate a "Sync Updates" task.

Additional Information

• For clusters using vLCM Cluster Images with NSX-T, refer to KB 316581 for additional steps required to re-upload NSX depots.
• To speak with a customer representative or a Support Engineer, see Contact Support.