Additional disk space expansion not recognized on VCF Operations for Networks Platform node.

Products

• VCF Operations for Networks

Issue/Introduction

After adding additional disk space to a VCF Operations for Networks Platform node,the disk is not recognized by the guest operating system or the appliance UI. This typically occurs when a virtual disk is expanded or added while the virtual machine (VM) is in a powered-off state.

• Added disk space from vCenter is not reflected in the output of df -h for /var partition.
• Running the sudo lsblk command reveals that the newly added disk (sdb in this example) is not currently part of any partition.
  
  
  
  
• The System Infrastructure Page continues to show old disk capacity.
• Disk expansion cron job (running every 5 minutes) fails to trigger.

Environment

VCF Operations for Networks 6.x
VCF Operations for Networks 9.x

Cause

The detection of newly added additional disk relies on a built-in cron job that runs every 5 minutes to automatically detect newly added disks. However, this automation only triggers upon a "hot-add" event (i.e., when a disk is added while the VM is powered on). If the disk size is increased while the VM is in powered-off state, the system will not detect the state change upon boot, leaving the partition at its original size.

Resolution

To prevent this issue, always ensure the VM is powered on when adding or expanding virtual disks. If the expansion was already performed while the VM was powered off and you do not see the new disk in the UI (or via the df -h command in the CLI), open a new case with Broadcom Support. Be sure to reference this KB article for manual intervention.