Error 'OUT_OF_VRP_CONFIGURED_MEMORY_RESOURCES' or OUT_OF_VRP_CONFIGURED_CPU_RESOURCES' when powering on VMs in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• Virtual machine power on fails with either one of the following errors in VMware Cloud Director(VCD)

  Internal Server Error  - ValidationException OUT_OF_VRP_CONFIGURED_MEMORY_RESOURCES Admission control failed for VRP: [name: OrgvDC VRP name ]
  Internal Server Error  - ValidationException OUT_OF_VRP_CONFIGURED_CPU_RESOURCES Admission control failed for VRP:  [name: OrgvDC VRP name ]

   

• OrgvDC has plenty of free memory and CPU resources available

• In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the Cloud Director cell, you see entries similar to:

  [ ######-####-####-###-########] Internal Server Error
   - Internal Server Error
   - ValidationException OUT_OF_VRP_CONFIGURED_MEMORY_RESOURCES Admission control failed for VRP:[name: OrgvDC VRP name (######-####-###-####-#####UUID), id: #####-####-####-####-#######] during deployment of VMs:[[[vcId=vCenter ID, moref=vm-vmmoref]]]. Total memory required for all VMs in the VRP including current VM being deployed [200MB] is greater than VRP maxResourceValue 100MB.
  
   com.vmware.ssdc.util.LMException: Internal Server Error
  at com.vmware.ssdc.util.LMException.wrap(LMException.java:###)
  at com.vmware.ssdc.library.ExceptionFactory.createFromMultiple(ExceptionFactory.java:##)
  at com.vmware.ssdc.backend.DeployVAppVmSubsetActivity.checkFuturesForException(DeployVAppVmSubsetActivity.java:###)
  at com.vmware.ssdc.backend.DeployVAppVmSubsetActivity$DeployNetworksPhase.invoke(DeployVAppVmSubsetActivity.java:###)

Environment

VMware Cloud Director version 10.x

Cause

This issue arises when changes are made to VM resources outside of VCD, resulting in a discrepancy between the computevm and vm_inv tables.

Resolution

Database modifications are required to correct and align inconsistent VM attribute values . To resolve this issue, please open a Support Request with Broadcom Technical Support and note this Article ID (386609) in the problem description. For more information, see Creating and managing Broadcom support cases.