Unable to save cluster image Error "Software Solution com.vmware.vsphere-wcp with version 8.0.#-######## cannot be found in depot."
search cancel

Unable to save cluster image Error "Software Solution com.vmware.vsphere-wcp with version 8.0.#-######## cannot be found in depot."

book

Article ID: 382522

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vSphere Kubernetes Service vSphere with Tanzu

Issue/Introduction

  • On update tab when validating the image set on respective cluster following error message will be observed :

"Software Solution com.vmware.vsphere-wcp with version 8.0.#-######## cannot be found in depot."

  • In /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log following entries will be reported with regards to the solution not being found in the Lifecycle manager of vCenter :

YYYY-MM-DDTHH:MM:SS info vmware-vum-server[3408962] [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 com.vmware.vsphere-wcp with version 8.0.#-######## cannot be found in depot.", "args": ["com.vmware.vsphere-wcp", "8.0.#-########"]}, "resolution": null, "time": "YYYY-MM-DDTHH:MM:SS"}]}
YYYY-MM-DDTHH:MM:SS info vmware-vum-server[3408962] [Originator@6876 sub=DraftsManager] [DraftsManager 1224] ValidateHardwareSupportSpec called

...

YYYY-MM-DDTHH:MM:SS error vmware-vum-server[3408962] [Originator@6876 sub=EntityImageManager] [EntityImageManager 103] [TranslateError] start
YYYY-MM-DDTHH:MM:SS error vmware-vum-server[3408962] [Originator@6876 sub=EntityImageManager] [EntityImageManager 113] [TranslateError] Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.softwarespec.SolutionNotFound<The specified solution is cannot be found in depots.>
-->
YYYY-MM-DDTHH:MM:SS error vmware-vum-server[3408962] [Originator@6876 sub=DraftsManager] [DraftsManager 1408] Failed to get config schemas for draft
YYYY-MM-DDTHH:MM:SS error vmware-vum-server[3408962] [Originator@6876 sub=DraftsManager] [DraftsManager 1489] Failed to validate cluster configuration
YYYY-MM-DDTHH:MM:SS error vmware-vum-server[3408962] [Originator@6876 sub=DraftsManager] [DraftsManager 1523] Failed to validate draft spec.

...

YYYY-MM-DDTHH:MM:SS warning vmware-vum-server[3398641] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
YYYY-MM-DDTHH:MM:SS info vmware-vum-server[3408962] [Originator@6876 sub=PM.AsyncTask.DraftCommitClusterTask{117}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.softwarespec.SolutionNotFound",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ],
-->    reason = "vLCM Task failed, see Error Stack for details."
-->    msg = "{
-->     "data": null,
-->     "error_type": "ERROR",
-->     "messages": [
-->         {
-->             "args": [],
-->             "default_message": "The specified solution is cannot be found in depots.",
-->             "id": "com.vmware.vcIntegrity.lifecycle.softwarespec.SolutionNotFound"
-->         }
-->     ]
--> }"
--> }

 

Cause

vSphere-wcp solution missing in the offline depot of vCenter's vLCM.

Resolution

1. While validating the image, the required vSphere-wcp version will be displayed in the error.

2. Open a case with Broadcom support team to have the right vsphere-wcp-depot.zip downloaded and imported to the vCenter's vLCM.

3. Upload vsphere-wcp-depot.zip to vLCM using vCenter lifecycle manager settings page :

4. Once upload is completed verify if the depot is created in the VUM server using the API (SSH into VC and run below dcli commands).

Note : Offline depot without any owner metadata is the newly uploaded depot ( owner value will also be the same as that of the user who uploads the vSphere-wcp-depot zip file ). Verify it’s content with the depot content API.

# dcli +show-unreleased com vmware esx settings depots offline list
<truncated>
<depot ID>:
   owner: [email protected]
   file_id: /storage/updatemgr/patch-store-temp/vum5704569949903948832.zip
   description:
   ownerdata:
   location:
   source_type: PUSH
<truncated>


# dcli +show-unreleased com vmware esx settings depots offline content get --depot <depot ID> +format json | jq -r '.metadata_bundles.vmw[0].solutions."com.vmware.vsphere-wcp".versions'
[
  {
    "display_version": "8.0.#",
    "version": "8.0.#-########" ------> This should match
  }
]

5. Verify if Spherelet Solution is already present or not for the respective cluster for which the image validation is failing ( After the upload of vsphere-wcp-depot.zip file if the same version is seen while running the below command just perform a validation of the image ).

# dcli +show-unreleased com vmware esx settings clusters software solutions list --cluster <cluster_moid>

6. Only proceed with this step to set the Spherelet solution on the cluster if the image validation fails again. (Can monitor the status of the set solution task from the UI also).

# dcli +show-unreleased com vmware esx settings clusters software solutions set-task --cluster <cluster_moid> --components '[{"component":"VMware-Spherelet-1-27"}]' --solution "com.vmware.vsphere-wcp" --version "8.0.#-########"

<Above command returns task_id>

7. Cluster compliance should now run successfully.

Powered by Wolken Software