Powering on virtual machines in VMware vCloud Director fails with the error: insufficient resources
search cancel

Powering on virtual machines in VMware vCloud Director fails with the error: insufficient resources

book

Article ID: 320414

calendar_today

Updated On:

Products

VMware VMware Cloud Director

Issue/Introduction

Symptoms:
  • Powering on virtual machines in VMware vCloud Director (vCD) fails
  • You see the error:

    Deployment of Virtual Machines in this Organization VDC has been disabled due to insufficient resources in the Provider VDC. Please contact the System Administrator
     
  • Cannot start any virtual machines in a Pay As You Go (PAYG) Organization VDC
  • Cannot start virtual machines even though resources are sufficient


Environment

VMware Cloud Director for Service Provider 9.x
VMware Cloud Director for Service Provider 9.0.x
VMware Cloud Director for Service Provider 5.6.x
VMware Cloud Director for Service Provider 8.x
VMware Cloud Director for Service Provider 5.x

Cause

This issue occurs when users overcommit the resources for a Provider vDC which contains PAYG Org vDCs.
The values for 'Total Reservation Sold' (for all vDCs in a given PvDC) should be less than Available Reservation in the PvDC Resource Pool.
 
As PAYG use Resources from the Provider VDC, it is possible for them to cause contention with the other Organization VDCs and as such are disabled when the PvDC Resources are not managed correctly.

Resolution

By default, vCloud Director ( vCD) disables all PAYG Power On operations as soon as the overcommitment occurs.
To resolve this issue, PAYG operations need to be re-enabled in the database.

Note: You should take a backup of your database before making any changes.
 
On the vCD Database execute this SQL query to re-enable PAYG operations:
Update Computehub_set SET paygo_deployment_status = 'ENABLED';

 
Note: It is possible to disable the vCloud check for the overcommitment, but this should only be done if you are able to correctly manage resources.
 
To disable the check for overcommitment, execute this SQL query on the vCD Database:
INSERT into config(CONFIG_ID,CAT,NAME,VALUE,SORTORDER) values((select max(config_id)+1 from config),'vcloud','EvdcPayGoAllocationModel.disableFurtherProvisioningOnOvercommit','false',0);
 

Restart all the Cell Services to ensure the changes take affect.


Powered by Wolken Software