VM total capacity inconsistencies when attaching a named disks in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

Inconsistencies in total disk capacity occur when attaching a Named Disk in VMware Cloud Director. VCD events report incorrect total disk capacity for multiple VMs, where the storageAllocationMb value lags by one operation, reflecting the previous storage state rather than the newly attached capacity. The correct total only appears in the subsequent modification event.

Sample event where the actual VM capacity is 1782GB but the event reports it as 1632GB:

'vm.description': '', 'vm. disksSizeMb': {'disk. name. Non-shared': '100', 'disk. name.Non-shared standard' : '150'}, 'metadata. system': {}, 'vm. cpuResourceMhz' : x, 'vm. storageProfile.id': {'id': 'xxxxxx-xxxx-xxxx-xxxx-xxxxxxxx'}, 'vm.memoryAllocationMb': 500, 'vm. storageAllocationMb' : 1632,

This event is generated for the VM when a named disk of 150GB is attached, but the total value reflects the previous event state.

Environment

VMware Cloud Director 10.6.x

Cause

VCD events are generated using the previously present storageAllocationMb value. Cloud Director does not fetch the updated storage metrics for the named disk from vCenter Server at the time the event is triggered

Resolution

Broadcom is aware of this issue and a fix is planned for an upcoming release of VMware Cloud Director.

Currently, there is no workaround available for this issue.