Inconsistencies in the total capacity used by hard disks on certain VMs as reported in the events in VCD UI.

Products

• VMware Cloud Director

Issue/Introduction

Whenever a hard disk is added or modified, the vm.storageProfile.name.Standard value in the event does not immediately reflect the updated total. Instead, the new value appears in a subsequent event, showing a delay in reporting the actual change.

Sample event where the actual VM capacity is 1.09 TB but the event reporting it as 634GB:

'vm.disksSizeMb': {'disk.name.worker3-os': '122880', 'disk.name.worker3-scsi1': '102400', 'disk.name.worker3-scsi2': '102400', 'disk.name.worker3-scsi3': '102400', 'disk.name.worker3-scsi4': '102400', 'disk.name.worker3-scsi5': '102400', 'disk.name.worker3-scsi6': '512000'},
'vm.storageProfile.name.Standard': 634880

 

Environment

VMware Cloud Director 10.x

Cause

This behavior occurs when events are generated before VMware Cloud Director (VCD) has updated storage usage or allocation information from vCenter, or when VCD processes the updated data with a delay.

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.