vLCM Cluster Compliance and HA Configuration Fails Due to Deleted /storage/updatemgr Directory
search cancel

vLCM Cluster Compliance and HA Configuration Fails Due to Deleted /storage/updatemgr Directory

book

Article ID: 442217

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • vSphere Lifecycle Manager (vLCM) cluster compliance checks fail with "cannot download/load depots" errors.
  • Additionally, attempts to modify or unconfigure vSphere HA at the cluster level fail with exceptions indicating "Solution being applied does not exist in the desired image" or com.vmware.vcIntegrity.lifecycle.SetSolutionTask.Failed.

Environment

vCenter Server 8x

Cause

The contents of the /storage/updatemgr partition were manually deleted. This results in the complete loss of downloaded patch metadata, vSphere HA agent solutions, and the specific directory ownership configurations required by the vmware-vum-server service to function.

Resolution

  1. Connect to the vCenter Server Appliance via SSH and login as root.

  2. Navigate to the Update Manager storage directory:

    cd /storage/updatemgr/

  3. Recreate the deleted directories and apply the strict ownership mappings required by vLCM and vSAN Health:

    mkdir -p hcl patch-store patch-store-temp plugins jetty-temp vsan
chown updatemgr:updatemgr .
chown -R updatemgr:updatemgr hcl/ patch-store/ patch-store-temp/ plugins/ jetty-temp/
chown -R vsan-health:root vsan/

  4. Reset the vLCM database to clear the orphaned image and depot caches:

    service-control --stop vmware-updatemgr
    /usr/lib/vmware-updatemgr/bin/updatemgr-util reset-db
    service-control --start vmware-updatemgr

  5. Restart the vSAN Health services to initialize the new database and directories:

    service-control --restart vmware-vsan-health

  6. Log in to the vSphere Client and navigate to Lifecycle Manager > Settings > Patch Setup.

  7. Re-authenticate and configure the official Broadcom Download Tokens. see kb Configuring the vSphere Lifecycle Manager Download Sources

  8. Initiate a manual Sync Updates task and wait for it to complete.

  9. Navigate to the affected cluster, turn vSphere HA OFF and then turn it back ON. This forces vCenter Server to recalculate the FDM agent deployment requirements and rebuild the solution state within the vLCM image map.

  10. Run a cluster compliance check to verify the issue is resolved.

Additional Information

Powered by Wolken Software