SDDC Manager health check fails with "resource lock" errors

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

• Running the command /opt/vmware/sddc-support/sos --health-check on the SDDC Manager appliance fails with an error indicating there are active locks for OPERATIONS_MANAGER.
  
  
  
  
  
• The SDDC Manager UI shows that all previous tasks have completed successfully.
  
  
• Certain UI operations, such as Host Commissioning or Backup Target editing, may be grayed out or disabled.
  
  
• Checking the SDDC Manager database shows entries in the lock table despite no active workflows.

Environment

VCF 5.x

VCF 9.0.x

Cause

This issue is caused by a stale lock entry in the SDDC Manager platform database. A previous workflow (such as a backup, upgrade, or health check) may have completed or timed out without properly clearing its entry from the lock table. This creates a mismatch where the system believes a resource is still in use.

Resolution

To resolve this issue, you must manually clear the stale lock from the database and restart the SDDC Manager services.

Note: Ensure you have a powered-off snapshot of the SDDC Manager VM before proceeding with database modifications.

1. Log in to the SDDC Manager appliance via SSH as the vcf user and switch to root using su -.
   
   
2. Identify the stale lock entries by running the following command:
    

   psql -h localhost -U postgres -d platform -c "select * from lock;"

   Example Output:

   psql -h localhost -U postgres -d platform -c "select id,resource_lock_type from lock;"

                        id             | resource_lock_type
      --------------------------------------+-----------------
   1#######-####-####-####-########### | EXCLUSIVE   
   2#######-####-####-####-########### | LIMITED
   3#######-####-####-####-########### | LIMITED
   4#######-####-####-####-########### | LIMITED

3. If there are locks present, delete the DB lock entries using the lock id from Step 2: 
   
   

   psql -h localhost -U postgres -d platform -c "delete from lock where id='1#######-####-####-####-###########';"

    
    
4. Restart the SDDC Manager services to re-sync the database change:
    

   /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

    

5. Verify the resolution by executing the health check again:
    

   /opt/vmware/sddc-support/sos --health-check