VCF Automation Shows Incorrect Capacity for Datastore Clusters Mapped to Storage Classes in a given region.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• In VMware Cloud Foundation (VCF) Automation, the total storage size is not correctly reflected for an assigned storage class within a given region.
• When a VM Storage Policy is applied to all datastores under a datastore cluster (storage pod), the VCF Automation user interface displays incorrect capacity values or intermittently shows only a hyphen (-) for total and used capacity.
• However, when the same storage policy is mapped to individual datastores outside of a datastore cluster, the capacity is calculated and displayed correctly in the VCFA UI.
• Navigation path: Navigate to VCF Automation Provider Management Page > Infrastructure > Regions > Select the Region to open > Storage Classes

Example:

The storage policy was applied to all datastores under a datastore cluster, which collectively provide 'X' TB of capacity.
However, when the storage policy is mapped to a region in VCFA, the total capacity displayed is 'Y' TB, instead of the expected 'X' TB or intermittently shows only a hyphen (-) for total and used capacity.

.

Environment

VCF Automation 9.0.x

VCF Automation 9.1.0

Cause

VCF Automation internal database inventory synchronization mechanism fails to automatically add missing storage pods (datastore clusters) into the primary datastore table during resource collection.

Resolution

Broadcom Engineering is aware of this issue and is working on fixing the issue in upcoming releases of VCF Automation.

To work around this behavior in version 9.0.2 without upgrading, apply the following method:

Avoid Datastore Clusters - Apply the target VM Storage Policy to individual standalone datastores within the vCenter instead of grouping them within a datastore cluster/storage pod.

Additional Information

vSphere Storage Policy Configuration Guidance