Internal Server Error when attempting to manage a VM in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• VMware Cloud Director (VCD) experienced issues connecting with vCenter.
• After successfully reconnecting to the underlying vCenter, attempts to manage virtual machines (VMs) result in tasks that fail with the following:
  
  Internal Server Error
  
  
• In the VCD container logs (/opt/vmware/vcloud-director/logs/vcloud-container-debug.log or vcloud-container-info.log), errors similar to the following are observed:
  
  xxxx-xx-xx xx:xx:xx,xxx | ERROR    | Backend-activity-pool-###7 | GenericVirtualResourcePool     | vrp ORG_NAME (####-####-####-####):####-####-####-#### - Failed to retrieve info of resource pool [vcId=#####-####-###-####-#######, moref=resgroup-#####]
  
  
• The resource pool referenced in the error (i.e., resgroup-#####) still appears to be correct in the underlying vCenter and the VM is not experiencing the issue in the following:
  
  Power on failed with error "Caused by: com.vmware.vcloud.fabric.compute.ResourcePoolNotFoundException"
  
  
• The resource pool does not appear in the VCD user interface (i.e., under Provider Interface >  Resources > Infrastructure Resources > Resource Pools).

Environment

VMware Cloud Director 10.6.x

Cause

Even though the resource pool still appears to be configured correctly in the underlying vCenter inventory, issues interacting with the vCenter caused VMware Cloud Director (VCD) to mark the object as deleted. Thus, when attempting to manage the virtual machine, VCD is unable to locate an active record for the associated resource pool.

Resolution

If the resource pool is still valid, the VMware Cloud Director database can be adjusted to mark the item as active to resume management of objects within it. Contact Broadcom Support and note this Article ID (415069) in the problem description. For more information, see Creating and managing Broadcom support cases.