Error: "Internal Server Error" and VM operations fail due to stale Resource Pool entries after merging vCenter Clusters in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

1. Powering on VMs or performing other VM operations in VMware Cloud Director fail with an "Internal Server Error".
2. This issue typically occurs after merging two physical vCenter clusters that were both already backing a Provider VDC in Cloud Director.
3. In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, you will see entries similar to the following, indicating a ResourcePoolNotFoundException:

   2026-08-20 10:41:08,207 | ERROR    | Backend-activity-pool-10  | GenericVirtualResourcePool     | vrp  (########-####-####-####-############):########-####-####-####-############ - Failed to retrieve info of resource pool [vcId=########-####-####-####-############, moref=resgroup-######]. | ...
   java.util.concurrent.ExecutionException: com.vmware.vcloud.fabric.compute.ResourcePoolNotFoundException
           at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:136)
           at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
   Caused by: com.vmware.vcloud.fabric.compute.ResourcePoolNotFoundException
           at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.getResourcePoolInfo(GenericVirtualResourcePool.java:1612)
           at com.vmware.vcloud.fabric.compute.vrp.AllocationPoolVirtualResourcePool.computeResourcePoolConfig(AllocationPoolVirtualResourcePool.java:282)

Environment

VMware Cloud Director 10.6.X

Cause

This issue can occur while merging clusters on a Provider VDC that is consuming those clusters, the Cloud Director database becomes out of sync in this case.

The org_prov_vdc and vrp_rp tables in the Cloud Director database continue to point to the legacy resource pools (sub_rp_moref) associated with the old compute hub, which no longer exist in vCenter.

Resolution

To resolve this issue, perform the following steps to force Cloud Director to sync resource pools:

1. SSH to the primary Cloud Director cell as root.
2. Run the detection command:

   /opt/vmware/vcloud-director/bin/cell-management-tool detect-rp-mismatches --detect-mismatch-with-vc --vdcs

3. If resource pool mismatches are detected, run the following command to attempt to fix the mismatches automatically:

   /opt/vmware/vcloud-director/bin/cell-management-tool detect-rp-mismatches --fix-mismatch-with-vc --vdcs

If the cell-management-tool commands do not resolve the issue, contact Broadcom Technical Support and note this Knowledge Article in the problem description, as the resolution requires a manual database edit to map the new Compute Hub IDs.

Additional Information

For more information, see How to Submit a Support Request.