When attempting to transition a vSphere cluster from vLCM Baseline (VUM) management to vLCM Image-based management using the PowerShell-based transition workflow, the operation fails during the image compliance check phase.
The PowerShell script reports the following error:
(ERROR) Check vLCM compliance for cluster "<cluster-name>" failed.
(ERROR) Cluster "<cluster-name>" is already being checked for image compliance. Skipping check.
Despite the cluster being in an active state and eligible for transition, the workflow does not proceed further.
SDDC Manager
The failure occurs due to stale or orphaned tasks/locks present in the SDDC Manager database.
In this scenario, an ACTIVE lock entry was found in the platform database, indicating an in-progress operation that was no longer valid. Although no active workflow was running, the lock prevented SDDC Manager from initiating a new vLCM image compliance check.
Example lock entry:
Connect to DB : psql -h localhost -U postgres -d platform
You are now connected to database "platform" as user "postgres".
platform=# \x
Expanded display is on.
platform=# select * from lock;
-[ RECORD 1 ] --
id | 56b5aa97-fe3d-4c74-9dd8-11225a105979
creation time 1769212800065
modification time | 1769212800065
error
locking context | {"serviceIdentifier": "Password Manager", "description": "Password management operation in progress. Please wait for completion", "pollingInterval":0, "expirationTime":0}
resource id
resource type | deployment
status ACTIVE
resource_name LEGACY
reentrant_key
resource_lock_type |
Because SDDC Manager detected the cluster as already undergoing a compliance check, the vLCM transition workflow was blocked.
To resolve the issue, identify and remove the stale lock from the SDDC Manager database.
Steps
psql -h localhost -U postgres -d platform
select * from lock;
delete from lock where id = '<lock-id>';
Confirm that the vLCM image compliance check completes successfully and the cluster transitions to image-based management.