CPU Allocation Used is higher than CPU quota in PAYG OrgVDC

Products

• VMware Cloud Director

Issue/Introduction

• The CPU Allocation Used value of the Organization VDC (OrgVDC) metrics visible in the Provider UI page Resources > Cloud Resources > Organization VDCs > [VDC_Name] > General > Metrics is higher value than expected.
• In the Tenant UI on the Data Centers page the CPU allocation used in the graph is higher than quota.

Environment

VMware Cloud Director 10.6.x

Cause

This issue can occur if some action has been performed outside the scope of Cloud Director by direct interaction within vCenter Server. 

For example, If there has been manual intervention made by an administrator to power on VMs directly in the vCenter Server UI. In a scenario where a VM power on failed in Cloud Director due to resource CPU allocation limit being hit, if an administrator accessed the vCenter Server UI directly and tried power on the VM there then it would successfully power on. The VM state would also switch to powered on in Cloud Director and the limit would be overridden. The CPU Allocation Used value in the OrgVDC would then show as higher than the quota.

Resolution

Review the VMs for the OrgVDC which are powered on in vCenter Server and Cloud Director and confirm if the sum of the CPU allocation for powered on VMs is equating to the value reported by Cloud Director.  If it's correct then it would confirm an action was taken at the vCenter layer to power on a VM.

It can also be of use In vCenter Server to see the CPU reservation Details for all VMs in the OrgVDC resource pool. To see this click on the resource pool object for the OrgVDC. Then navigate to Monitor > Resource Allocation > CPU. Review the VM CPU information available and check for discrepancies such as a higher than expected CPU reservation on VMs.