Manually re-creating and linking the System VDC and other VDC Resource Pools after the Resource Pools were deleted in vCenter

Products

• VMware Cloud Director

Issue/Introduction

• User incorrectly deleted the System vDC Resource Pool in vCenter.
• The System vDC Resource pool does not exist in vCenter.
• User disabled DRS in vCenter.
• Cloud Director cannot deploy any System VMs 
• In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, you see entries similar to:

<YYYY-DD-MM><time> | DEBUG | LocalTaskScheduler-Pool-5 | AbstractVlsiServiceBehavior | instantiation VCenterVimVlsiServiceBehaviorImpl@34bf41c2 for key <example key value UUID> | vcd=<VCD_UUID>,task=<TASK_UUID>
<YYYY-DD-MM><time> | ERROR | LocalTaskScheduler-Pool-5 | VcRetrievePropertiesProvider | Retrieve property failed for moref resgroup-####| vcd=<VCD_UUID>,task=<TASK_UUID> com.vmware.vim.binding.vmodl.fault.ManagedObjectNotFound: obj = com.vmware.vim.binding.vmodl.ManagedObjectReference@######## inherited from com.vmware.vim.binding.vmodl.fault.ManagedObjectNotFound: The object has already been deleted or has not been completely created

Environment

• 9.x
• 10.x

Cause

• This issue occurs when actions are taken outside of Cloud Director which result in Resource Pools being deleted and/or recreated.
  • Such actions include
    • A Resource Pool is deleted by a user.
    • DRS is disabled by a user.
• Cloud Director will never attempt to disable DRS in vCenter.

Resolution

Note: Prior to 10.4.1, if the customer completely disabled DRS, the customer must revert their VCD, VC and NSX Databases to the last time they were in sync. There is no mechanism by which we can recreated and re-link the various Resource Pools and references in the Database in Cloud Director 10.4 GA and earlier.

 

If using 10.4.1 and later, customers can use the Cell-Management-Tool option to fix the mismatch.

• Detect and Fix Resource Pool Mismatches between VMware Cloud Director and vCenter
  • The above is a best effort to help resolve and issue introduced outside of the scope of Cloud Director.
  • If you are still encountering issues post running the above Cell-Management-Tool option, please revert the VCD, VC and NSX Databases to the last time they were in sync

Additional Information