vCenter 9 - failed to unconfigure HA - setting solution for image failed.

Products

• VMware vCenter Server

Issue/Introduction

When configuring vSphere HA - it fails on unconfiguring stage and provides error: "setting solution to image failed"

Environment

VCF 9.x

vCenter 9.x

Cause

Reviewing the  /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log - we see "HA depot is not load yet" and "Setting solution for image failed".

 

2025-11-04T16:30:32.213Z info vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 156] Check depot for solution: com.vmware.vsphere-ha_9.0.0-249574
54
2025-11-04T16:30:32.216Z info vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 170] HA depot is not load yet
2025-11-04T16:30:32.216Z error vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 185] Failed to set solution on domain-c12345. Reason: HA depot not loaded yet
2025-11-04T16:30:32.216Z info vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 505] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5257a206-b90f
-3f1a-581a-5fc5deac793a. Finalizing Task
2025-11-04T16:30:32.216Z info vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 345] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5257a206-b90f
-3f1a-581a-5fc5deac793a. Task Finalization completed.
2025-11-04T16:30:32.216Z error vmware-vum-server[13797] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 424] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5257a206-b90
f-3f1a-581a-5fc5deac793a. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.SetSolutionTask.Failed<Setting solution for image failed.>

Resolution

Snapshot vCenter

 

Reset update manager database as per this KB below

 

Also - because this is VCF 9 and NSX is involved, the workaround in this KB below for this also needs to be applied

 

Resetting the VMware Update Manager Database
https://knowledge.broadcom.com/external/article/316581/resetting-vmware-update-manager-database.html