Project Quota Displays Incorrect VM Count After Deletion
Article ID: 407452
Updated On:
Products
Issue/Introduction
Customers using VMware Aria Automation may observe that the VM quota displayed at the project level does not accurately reflect the current number of deployed virtual machines, particularly after VMs have been deleted.
For example, if a project is configured with a quota to deploy 30 machines and currently has 18 VMs provisioned, deleting 3 of these VMs might not immediately update the project's displayed VM count. The system may continue to show 18 VMs, even though only 15 are actively running. This discrepancy can lead to confusion regarding available project resources and may impact further provisioning.
Environment
Aria Automation 8.18.x
Cause
The discrepancy often arises because the project-level quota count, while intended to be dynamic, might not always refresh immediately upon VM deletion. The system performs periodic recalculations, but in some cases, a manual intervention is required to force an update.
Resolution
Workaround:
1. Verify Current Project VM Count via API: You can check the VM count that the Aria Automation UI and internal systems use for project quotas by calling the following API endpoint:
GET https://automationFQDN/iaas/api/projects?$filter=name eq 'Your Project Name'- Replace automationFQDN with the fully qualified domain name of your Aria Automation instance.
- Replace 'Your Project Name' with the exact name of the project experiencing the issue (e.g., 'Dev Project').
This API call returns details for your project, including an attribute like allocatedInstancesCount, which reflects the VM count seen at the project level. If this number does not match the actual number of active, non-deleted VMs in your project, a recalculation is necessary.
2. Force Quota Recalculation with a Script: If you observe a difference between the allocatedInstancesCount reported by the project API and the actual number of active VMs in your project, a specific script can be used to force a recalculation of the project's allocation ID. This script triggers an internal API call that updates the VM count for the specified project.
Once you have obtained the script (as detailed in step 3), you would execute it from your Aria Automation appliance or a system with API access:
./recalculateAllocationId.sh [Project_UUID]3. Obtaining the Recalculation Script:
The recalculateAllocationId.sh script is not publicly distributed. If you are experiencing this issue and require the script, please raise a support ticket with Broadcom Global Support Services (GSS). Broadcom GSS will assess your environment and provide the necessary script along with guidance for its secure execution.
Additional Information
Important Note: Always ensure you have a proper backup before performing any manual interventions or running scripts provided by support. If you are unsure about any steps, please contact Broadcom GSS for assistance.
Feedback
