vLCM Image Compliance Fails with Error: Specified Solution Cannot Be Found in Depots for vCenter Server

Products

• VMware vCenter Server 8.0

Issue/Introduction

• This article addresses instances where vSphere Lifecycle Manager (vLCM) image compliance fails with the below error state, preventing essential component validation and causing vSphere HA degradation.

Specified Solution Cannot Be Found in Depots" or when the vLCM service enters an "Unhealthy

• vSphere Lifecycle Manager (vLCM) service remains in an "Unhealthy" state and fails to start.

• Remediation of image-based clusters fails with: 

  Software Solution [Component] cannot be found in depot.

• vSphere High Availability (HA) fails to initialize or appears degraded.

• Log entries in vmware-updatemgr.log show com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound.
•  

/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log confirms that vLCM fails when validating the image specification and throws the following errors

####-##-##T##:##:##.#### info vmware-vum-server [25450] [Originator@6876 sub=VumVapi: :Utils] [DepotContentManager 686] GetCachedDepotComponent called.
####-##-##T##:##:##.#### error vmware-vum-server [25450] [Originator@6876 sub-VumVapi: :Utils] [DepotContentManager 727] Solution component should NOT be visible. Treat as NotFound
####-##-##T##:##:##.#### warning vmware-vum-server [25450] [Originator@6876 sub=DepotManager: : SoftwareSpecUtil] [SoftwareSpecUtil 505] Component not found in the depot. Name: 'vsphere-fdm', Version: '8.0.3-24853646'
####-##-##T##:##:##.#### info vmware-vum-server [25450] [Originator@6876 sub=DepotManager: :SoftwareSpecUtil] [SoftwareSpecUtil 612] GetSolutionInfoForSpec called.
####-##-##T##:##:##.####info vmware-vum-server [25450] [Originator@6876 sub=VumVapi: :Utils] [DepotContentManager 1703] GetComponentDetailsByName called.

 

Environment

• VMware vCenter Server 8.0.x

Cause

The issue is triggered by metadata corruption within the vSphere Lifecycle Manager (vLCM) depot database. Stale or orphaned entries in the database prevent Lifecycle Manager from properly mapping solutions to existing depot entries, causing the service startup and validation sequences to fail.

Resolution

IMPORTANT: Before proceeding, take a snapshot of the vCenter Server Appliance.

1. SSH to the vCenter Server as root.
2. If not already in the shell, run: 

   shell

3. Stop the VMware Update Manager service: 

   service-control --stop vmware-updatemgr

4. Reset the VMware Update Manager database: 

   python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db

5. Delete the contents of the patch store: 

   rm -rf /storage/updatemgr/patch-store/*

6. Restart the VMware Update Manager service: 

   service-control --start vmware-updatemgr

Additional Information

• If this issue persists after performing these steps, please ensure all applicable patches are applied. See Download Broadcom products and software to download the latest releases.
• To speak with a customer representative or a Support Engineer see Contact Support