YYYY-MM-MMTHH:MM:HH.SSSZ error vmware-vum-server[55553] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 412] Set solution failed. entityId: domain-c#### Problems found while validating the new software spec: {
--> "errors": [
--> {
--> "id": "com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionNotFound",
--> "message": {
--> "args": [
--> "com.vmware.nsxt",
--> "9.0.2.0-25150387",
--> "",
--> ""
--> ],
--> "default_message": "Software Solution com.vmware.nsxt with version 9.0.2.0-25150387 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-MMTHH:MM:HH.SSS",
--> "type": null
--> }
--> ],
--> "info": [],
--> "warnings": []
--> }This issue occurs when the vSphere Lifecycle Manager (vLCM) depot metadata is inconsistent or missing a specific solution version that the cluster's desired image is attempting to validate. This is common after a vCenter patch where the image validation process looks for components (like NSX-T agents) that are not currently synchronized in the local depot.
Option 1: Cluster Image Revalidation
Option 2: API-Based Depot Cleanup
Open the vSphere UI, navigate to Developer Center -> API Explorer
GET /api/esx/settings/depots/offline.com.vmware.nsxt:9.0.2.0-####) mentioned in the logs.DELETE /api/esx/settings/depots/offline/{depot}?vmw-task=true and execute using the identified ID. service-control --restart vmware-updatemgr