"Software Solution VMware-HBR-Agent cannot be found in depot" error during vSphere Cluster Single Image Configuration

Products

VMware vCenter Server

Issue/Introduction

When attempting to configure a vSphere cluster to use a single image, the operation fails and displays an error message indicating that a required software solution cannot be found in the depot.

Error: Software Solution VMware-HBR-Agent with version 8.0.2-0.0.22435776 cannot be found in depot.
The vSphere Lifecycle Manager is reporting a SolutionNotFound error (com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound) during image validation.

/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

2025-10-31T06:01:11.785Z info vmware-vum-server[3227853] [Originator@6876 sub=ServiceProvider] [ImageService 372] Run command: --taskid 52d15296-d833-274f-a20f-2e1d2a30b2dd --threadid 3227853 software --validate
2025-10-31T06:01:11.790Z info vmware-vum-server[3227853] [Originator@6876 sub=ServiceProvider] [EmbeddedPyServiceProvider 1548] Draft validation results: {"info": [], "warnings": [], "errors": [{"id
": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound", "message": {"id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound", "default_message": "Software Solution VMware-HBR-Agen
t with version 8.0.2-0.0.22435776 cannot be found in depot.", "args": ["VMware-HBR-Agent", "8.0.2-0.0.22435776"]}, "resolution": null, "time": "2025-10-31T06:01:11.790Z"}]}
2025-10-31T06:01:11.791Z info vmware-vum-server[3227853] [Originator@6876 sub=DraftsManager] [DraftsManager 1224] ValidateHardwareSupportSpec called
2025-10-31T06:01:11.791Z info vmware-vum-server[3227853] [Originator@6876 sub=DraftsManager] [DraftsManager 1586] Draft validation results: {
--> "errors": [
--> {
--> "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
--> "message": {
--> "args": [
--> "VMware-HBR-Agent",
--> "8.0.2-0.0.22435776"
--> ],
--> "default_message": "Software Solution VMware-HBR-Agent with version 8.0.2-0.0.22435776 cannot be found in depot.",
--> "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
--> "localized": null,
--> "params": null
--> },
--> "originator": null,
--> "resolution": null,
--> "retriable": null,
--> "time": "2025-10-31T06:01:11.790Z",
--> "type": null
--> }
--> ],
--> "info": [],
--> "warnings": []
--> }
2025-10-31T06:01:11.791Z error vmware-vum-server[3227853] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DraftCommitClusterTask] [CommitDraftTask 328] Draft commit failed for the entityId: d
omain-c2309958 Problems found while validating the new software spec: {
--> "errors": [
--> {
--> "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
--> "message": {
--> "args": [
--> "VMware-HBR-Agent",
--> "8.0.2-0.0.22435776"
--> ],
--> "default_message": "Software Solution VMware-HBR-Agent with version 8.0.2-0.0.22435776 cannot be found in depot.",
--> "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
--> "localized": null,
--> "params": null
--> },
--> "originator": null,
--> "resolution": null,
--> "retriable": null,
--> "time": "2025-10-31T06:01:11.790Z",
--> "type": null
--> }
--> ],
--> "info": [],
--> "warnings": []
--> }

Environment

VMware vSphere 8.x

Resolution

**Note: Take snapshot of the vCenter server before making any change, see "Snapshot Best practices for vCenter Server Virtual Machines" and "VMware vCenter in Enhanced Linked Mode pre-changes snapshot (online or offline) best practice" for more information.

Steps to follow to remove the unwanted module from VCDB to fix the reported issue:

Login to vCenter Server SSH with root credentials.
Enter 'shell'
Use the following command to check the status of the Update Manager service on the vCenter Server Appliance (VCSA):
service-control --status vmware-updatemgr
If the service is stopped, start it manually using:
service-control --start vmware-updatemgr
If the service is running, proceed to the next step in your workflow.
1. Note down the db_password from the below command.
  cat /usr/lib/vmware-updatemgr/bin/configvalues.txt
2. Switch to vumuser using the below command
  #su - updatemgr -s /bin/bash
3. Run the below command and enter the password from previous step.
  /opt/vmware/vpostgres/current/bin/psql -d VCDB -U vumuser
4. Run the command to get the current config (highest number associated with the config is the current active state)
  VCDB=> select * from pm_software_desired_states;
5. Once logged in as vumuser, run the following command(remove the unwanted config segment under solutions.components)
```
update pm_software_desired_states set spec = '{
  "add_on": {
    "name": "DEL-ESXi",
    "version": "802.22380479-A00"
  },
  "alternative_images": null,
  "base_image": {
    "version": "8.0.2-0.0.22380479"
  },
  "components": null,
  "hardware_support": null,
  "removed_components": null,
  "solutions": {
    "com.vmware.vsphere-ha": {
      "components": [
        {
          "component": "vsphere-fdm"
        }
      ],
      "version": "8.0.2-23504390"
    }
  }
}' where entity_id='domain-c2309958' and desired_state_id=73;
```
You're expected to see UPDATE 1 upon successful execution of the above DB query.
Retry configuring the cluster with single image.