Attempting to refresh VCF Automation's connection to vCenter fails with "The entity vCenter Server is busy completing an operation"

Products

• VCF Automation

Issue/Introduction

Attempting to refresh the VCF Automation connection to vCenter fails. When selecting the vCenter and choosing to refresh the connection, the failed task in the user interface presents the following error:

com.vmware.vcloud.api.presentation.service.BusyEntityException: The entity vCenter Server is busy completing an operation . at com.vmware.vcloud.backend.spbmeventlistener.RefreshStorageClassesActivity$CollectStorageProfilesPhase$2.recover(RefreshStorageClassesActivity.java:152)

The vCenter is busy error will occur when there a failed task causing an uncleared lock. 

Checking the tenantmanager log files from a support bundle collected for VCFA: /tenant-manager-1/vclistener/file-log-#####.log shows entries similar to:

Conversation opened at: <undefined> | requestId=cdb83646-####-####-####-a5dc55c38585,request=POST https://<vCenterFQDN>/api/admin/extension/vimServer/6661b853-####-####-####-f1fb00e942ae/action/refresh,requestTime=1777928202370,remoteAddress=<vCenterIP>:46082,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+json;version 41.0.0-alpha,Host=<vCenterHostname> vcd=b2363d4b-####-####-####-82c35219b603,task=ff97ffa3-####-####-####-d24c76eb2035 activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:ff97ffa3-####-####-####-d24c76eb2035) activity=(com.vmware.ssdc.backend.services.RefreshVcenterActivity,urn:uuid:7d9fadd0-a97d-45f4-a573-e1618a4c91fb) activity=(com.vmware.ssdc.backend.RefreshSupervisorsInventoryActivity,urn:uuid:719691cb-####-####-####-f0e29eb81d39) activity=(com.vmware.vcloud.backend.spbmeventlistener.RefreshStorageClassesActivity,urn:uuid:ddccd86f-####-####-####-9e13e4b97749)
2026-05-04 20:56:56,827 | ERROR | Backend-activity-pool-53 | JDBCExceptionReporter | Batch entry 0 /* Method: unknown / / Method: unknown / / insert com.vmware.vcloud.common.model.LockIntentModel */ insert into lock_intent (cell_instance_id, thread_id, object_id, object_lock_type) values (('489'::int4), ('810'::int8), ('6661b853-6d25-4843-897f-f1fb00e942ae'::uuid), ('4'::int4)) was aborted: ERROR: duplicate key value violates unique constraint "intent_object_type_id"
Detail: Key (object_lock_type, object_id)=(4, 6661b853-####-####-####-f1fb00e942ae) already exists. Call getNextException to see other errors in the batch. | requestId=cdb83646-####-####-####-a5dc55c38585,request=POST https://<vCenterFQDN>/api/admin/extension/vimServer/6661b853-####-####-####-f1fb00e942ae/action/refresh...

Further down in the same log the busy exception is logged:

2026-05-04 20:56:57,621 | ERROR | Backend-activity-pool-53 | VirtualCenterService | An active spbm data collection on 6661b853-###-####-####-f1fb00e942ae is running. 
...
com.vmware.ssdc.library.exceptions.LMObjectBusyException: The object you selected is currently busy. Try again in a few minutes.

Environment

VCF Automation 9.0.x

Cause

A storage policy naming conflict in the database prevents the connection refresh from succeeding, which subsequently creates an orphaned database lock on the vCenter object in the tenantmanager database. This persistent lock causes all future refresh operations to fail with an LMObjectBusyException.

Resolution

• Create a support case with Broadcom support and reference this KB article 440300.