vLCM Image Compliance Fails with Error: “Specified Solution Cannot Be Found in Depots”
search cancel

vLCM Image Compliance Fails with Error: “Specified Solution Cannot Be Found in Depots”

book

Article ID: 411089

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

Symptoms:

  • Remediation of an image-based standalone host (not part of a cluster) fails with the error:
    “Software Solution VMware-HBR-Agent with version 8.0.3-0.0.24299508 cannot be found in depot.”

  • The HBR component is present in the image depot.

  • Manual import of the component reports it already exists.

  • Manual removal and reinstallation of the HBR Agent component to the relevant cluster images in Lifecycle Manager was performed, but the issue persisted.

var/log/vmware/vmware-updatemgr/vum-server.log confirms that vLCM fails when validating the image specification and throws the following errors

 
YYYY-MM-DDTHH:MM:SSZ error vmware-vum-server[3462980] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:52eec97d-####-####-####-#########. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.invalid_argument
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound<Software Solution VMware-HBR-Agent with version 8.0.3-0.0.24299508 cannot be found in depot.>
-->    com.vmware.vcIntegrity.lifecycle.softwarespec.InvalidImage<Image is not valid.>
-->
YYYY-MM-DDTHH:MM:SSZ warning vmware-vum-server[3449382] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
YYYY-MM-DDTHH:MM:SSZ info vmware-vum-server[3462980] [Originator@6876 sub=PM.AsyncTask.SetSolutionTask{1030203}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "VMware-HBR-Agent"
-->             },
-->             (vmodl.KeyAnyValue) {
-->                key = "2",
-->                value = "8.0.3-0.0.24299508"
-->             }
-->          ],
-->          message = <unset>
-->       },
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.softwarespec.InvalidImage",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ],
-->    reason = "vLCM Task failed, see Error Stack for details."
-->    msg = "{
-->     "data": {
-->         "notifications": {
-->             "errors": [
-->                 {
-->                     "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
-->                     "message": {
-->                         "args": [
-->                             "VMware-HBR-Agent",
-->                             "8.0.3-0.0.24299508"
-->                         ],
-->                         "default_message": "Software Solution VMware-HBR-Agent with version 8.0.3-0.0.24299508 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:SSZ",
-->                     "type": null
-->                 }
-->             ],
-->             "info": [],
-->             "warnings": []
-->         }

Environment

VMware vCenter Server 8.X

Cause

The issue is triggered by a discrepancy in the vLCM database that prevents Lifecycle Manager from properly mapping the solution to the existing depot entry.

Resolution

Follow the below workaround to resolve the issue

Reset the VMware Update Manager (VUM) database to resolve the corruption and reinitialize the depot mapping.

  1. SSH to the vCenter as root.

  2. Switch to BASH shell if not already in it:

     
    #shell
  3. Stop the VMware Update Manager Service:

     
    #service-control --stop vmware-updatemgr
  4. Reset the VMware Update Manager Database:

    • For vCenter Server Appliance 8.0:

       
      #python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db

     

  5. Delete the contents of the VMware Update Manager Patch Store:

     
    #rm -rf /storage/updatemgr/patch-store/*
  6. Restart the VMware Update Manager Service:

     
    #service-control --start vmware-updatemgr