Provisioning Fails Due to Incorrect Storage Allocation in Group Resource Placement (GRP)
search cancel

Provisioning Fails Due to Incorrect Storage Allocation in Group Resource Placement (GRP)

book

Article ID: 423318

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Provisioning operations in VMware Aria Automation 8.x fail due to incorrect storage resource calculations. The Group Resource Placement (GRP) service incorrectly reports negative available storage, even when no corresponding disks exist in the physical environment.

This condition creates a "hard block" on new provisioning requests, triggering errors related to insufficient storage capacity.

Environment

VMware Aria Automation 8.x

Cause

The root cause is the presence of stale storage allocation records within the GRP database.

When disks are provisioned and subsequently deleted, detached, or retired, the associated storage allocations should be released. However, in this scenario, the allocations remain "orphaned." Because GRP continues to account for these non-existent disks, the internal counters become desynchronized, eventually leading to a negative availability state.

Resolution

This issue cannot be resolved through automatic background reconciliation. It requires a manual repair of the Group Resource Placement (GRP) state using the API.

Workaround / Repair Steps

  1. Generate a Bearer Token: Use your administrative credentials to generate a valid bearer token for API authentication.

  2. Run the GRP Repair API: Execute a POST request to the repair endpoint to force a recalculation of storage allocation counters. This removes orphaned records and aligns GRP with the actual disk state.

Example API Call:

curl -X POST https://<host>/provisioning/mgmt/placement/group-resource-placement/<groupResourcePlacementId>/repair \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json"

Note: Replace <host>, <token>, and <groupResourcePlacementId> with your environment's specific values.

  1. Verify the Fix:

    • Ensure Available Storage is no longer a negative value.
    • Confirm Allocated Storage accurately matches the capacity of existing disks.
    • Test a new provisioning request to ensure it completes successfully.

Additional Information

If the Repair API Does Not Resolve the Issue:

  • Inspect the GRP state to confirm if allocated storage values persist without corresponding disk entries.

  • Collect diagnostic output from both the GRP and provisioning APIs.

  • Engage Broadcom/VMware Support or your engineering team with these details for deeper database analysis.

Powered by Wolken Software