Software Solution com.vmware.vsphere-wcp with version 9.0.1.32.5.0-25065159 cannot be found in depot during VCF 9.1 ESX cluster upgrade

Products

• VCF Operations
• VMware vCenter Server

Issue/Introduction

• Performing a cluster upgrade or modifying a cluster image, the validation task may fail

Task: Create and Commit draft check fails.
Description: Verifies that the target image specification for the cluster is successfully created and committed.
Result: Failed to invoke create and commit the desired state image spec.

• /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log (on vCenter)

YYYY-MM-DDTHH:MM:SS INFO vmware-vum-server <>[vc@4413 sub="com.vmware.vcIntegrity.lifecycle.ValidateDraftTask"] [ValidateDraftTask, 288] 
Task:com.vmware.vcIntegrity.lifecycle.ValidateDraftTask ID:<Task ID>. Draft validation succeeded, Notifications: {
      "errors": [
          {
              "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
              "message": {
                  "args": [
                      "com.vmware.vsphere-wcp",
                      "9.0.1.32.5.0-25065159",
                      "",
                      ""
                  ],
                  "default_message": "Software Solution com.vmware.vsphere-wcp with version 9.0.1.32.5.0-25065159 cannot be found in depot.",


• spherelet version on the ESX host (ssh session)

[root@esx:~] localcli software vib list | grep -i spherelet

spherelet        9.0.1.32.5.0-25065159      VMware  VMwareCertified   YYYY-MM-DD    host

Environment

VCF 9.x

Cause

The issue is caused by an obsolete or inconsistent Workload Control Plane (WCP) offline depot remaining registered on the vCenter Server. This stale repository creates a metadata conflict that prevents vSphere Lifecycle Manager (vLCM) from correctly staging the WCP VIBs (Spherelet) for the target ESXi image.

Resolution

Proceed to reload the WCP offline depot on vCenter

1. Log in to the vCenter Server Appliance (VCSA) via SSH
2. List all registered offline repositories using dcli:
   
   

   dcli com vmware esx settings depots offline list

   
   Note: Locate the IDs associated with ownerdata as com.vmware.vsphere-wcp
   
   Sample:
   
   B0B9326BD84BA41BCE40538B89669E243D6C707E:
   owner: com.vmware.vcIntegrity
   file_id: /storage/updatemgr/patch-store-temp/vsphere-wcp-depot-embedded.zip
   description: WCP offline bundle
   ownerdata: com.vmware.vsphere-wcp
   location:
   source_type: PUSH
   
   
3. Delete all the offline repositories for wcp
   
   

   dcli com vmware esx settings depots offline delete --depot <DEPOT_ID> --force true

   Sample:
   
   dcli com vmware esx settings depots offline delete --depot B0B9326BD84BA41BCE40538B89669E243D6C707E --force true
   
   
4. Proceed to restart the below services
   
   

   service-control --restart updatemgr && service-control --restart wcp

5. Return to the vSphere Client or VCF Operations UI and retry the cluster image validation/commit task

 

If the above steps do not resolve the issue, ensure the Supervisor Release Content Library is configured to "Download all library content immediately" and perform a manual synchronisation. If set to "Download library content only when needed", vLCM may fail to validate components because the binaries have not been pulled to the local vCenter storage, resulting in "Software Solution not found" errors.

After the change is made, you may need to follow the steps outlined in the KB again to resolve the issue.