"Software Solution com.vmware.vsphere-wcp with version <version string> cannot be found in depot" and WCP depots may not be loaded
search cancel

"Software Solution com.vmware.vsphere-wcp with version <version string> cannot be found in depot" and WCP depots may not be loaded

book

Article ID: 313477

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • WCP solution set task fails with: "A general system error occurred: Image is not valid".

    YYYY-MM-DDTHH:MM:SS.##Z info vmware-vum-server[31725] [Originator@6876 sub=DraftsManager] [DraftsManager 1468] Draft validation results: {
    -->     "errors": [
    -->         {
    -->             "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
    -->             "message": {
    -->                 "args": [
    -->                     "com.vmware.vsphere-wcp",
    -->                     "8.0.0-59967719"
    -->                 ],
    -->                 "default_message": "Software Solution com.vmware.vsphere-wcp with version 8.0.0-59967719 cannot be found in depot.",
    -->                 "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
    -->                 "localized": null,
    -->                 "params": null
    -->             },
    -->             "originator": null,
    -->             "resolution": null,
    -->             "retriable": null,
    -->             "time": "YYYY-MM-DDTHH:MM:SS.##Z",
    -->             "type": null
    -->         }
    -->     ],
    -->     "info": [],
    -->     "warnings": []
    --> }

Environment

  • VMware vCenter Server 7.x
  • VMware vCenter Server 8.x
  • VMware vCenter Server 9.x

Cause

When the vpxd service starts slower than the VUM service, the VUM service restarts itself. When it restarts, the running tasks are cancelled including the WCP offline bundle loading. As a result, the restarted VUM service doesn't have WCP depot loaded. The WCP solution set task will fail with the errors mentioned above.

Resolution

Currently there is no resolution to the issue.


Workaround:

  1. SSH in to the vCenter
  2. Restart the updatemgr service by running the following command.
    vmon-cli -r updatemgr