Extend root and alt_root volumes on VMware Aria Suite Lifecycle appliance for versions 8.12.x and later

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The used space in the root volume of your VMware Aria Suite Lifecycle is reaching the total size which can cause system failure because of no free space.
• Applying patch of upgrading VMware Aria Suite Lifecycle Manager fails due to lack of space on the appliance.
• This KB article applies only if you are running VMware Aria Suite Lifecycle Manager appliance that was deployed as 8.12.x or later version.  This KB does not apply to VMware Aria Suite Lifecycle Manager that was upgraded to 8.12.x or later version from a version earlier than 8.12.x. 
• This KB article applies only when the disk structure is as follows when running the command lsblk:

Environment

VMware Aria Suite Lifecycle 8.12.x and later

 

Resolution

*Do NOT apply the below steps to VMware Aria Suite Lifecycle appliances that were initially deployed on a version lower than 8.12. The steps outlined below are NOT suitable for VMware Aria Suite Lifecycle appliances that were upgraded to 8.12.x.  Applying these steps to incorrect versions of VMware Aria Suite Lifecycle can result in data loss.

Prerequisites 

• Ensure that Aria Suite Lifecycle was deployed on version 8.12 and above
• Make sure to clone or take a backup of Aria Suite Lifecycle Manager appliance before proceeding with the below steps.
• Before the procedure snapshots should be removed.

Steps

• Log in to the vSphere UI and locate the Aria Suite Lifecycle Manager VM.
• Right-click the VM and select Edit Settings from the Actions menu.
• In the Virtual Hardware tab, find and expand the menu for Hard Disk 1 (root) and Hard Disk 5 (alt_root). The alt_root disk should be big enough to fit the size of the root logical volume (after the resize) and the LVM metadata. The first disk that should be expanded should be be Hard Disk 1 and the other should be Hard Disk 5. 
• Reboot Aria Suite Lifecycle Manager appliance once the reconfigure VM task in vSphere has completed successfully and check that the system has detected the expanded disks. This can be verified using the lsblk command.
• Record the output from the commands below:

• • lsblk
  • cat /etc/fstab
  • fdisk -l

• To resize the partition on disk run the below command:

parted /dev/sda resizepart 4 100% 
   
Example Output: [ ~ ]# parted /dev/sda resizepart 4 100%
Information: You may need to update /etc/fstab.

• Run the below command to get the disk allocation in MB:

lsblk -b -o NAME,SIZE | awk 'NR==1 {print $0 " (MB)"} NR>1 {printf "%-10s %d MB\n", $1, $2/1024/1024}'

Example Output:
[ ~ ]# lsblk -b -o NAME,SIZE | awk 'NR==1 {print $0 " (MB)"} NR>1 {printf "%-10s %d MB\n", $1, $2/1024/1024}'
NAME                                     SIZE (MB)
sda        15360 MB
├─sda1     4 MB
├─sda2     10 MB
├─sda3     512 MB
└─sda4     14832 MB  <<<<<< (SIZE-IN-MB)
└─system-system_0 10236 MB
sdb        51264 MB
└─data-data_0 51200 MB
sdc        10304 MB
└─storage-storage_0 10240 MB
sdd        8256 MB
└─swap-swap_0 8192 MB
sde        15360 MB
└─vg_alt_root-lv_alt_root 10240 MB
sdf        8256 MB
└─vg_lvm_snapshot-lv_lvm_snapshot 8192 MB
sr0        1023 MB

• Perform pvresize on "/dev/sda4"

pvresize /dev/sda4 --setphysicalvolumesize <SIZE-IN-MB>
   
NOTE : Get the value for 'SIZE-IN-MB' from the output of previous command (lsblk -b -o NAME,SIZE | awk 'NR==1 {print $0 " (MB)"} NR>1 {printf "%-10s %d MB\n", $1, $2/1024/1024}')

• Perform lvextend on /dev/system/system_0

lvextend -r -l +100%FREE /dev/system/system_0

• Resize the physical volume on /dev/sde using pvresize. The goal is to make its size identical to the physical volume size of /dev/sda4.

pvresize /dev/sde --setphysicalvolumesize <SIZE-IN-MB>
 
NOTE : Provide the same "SIZE-IN-MB" value mapped to "sda4" partition from output of command (lsblk -b -o NAME,SIZE | awk 'NR==1 {print $0 " (MB)"} NR>1 {printf "%-10s %d MB\n", $1, $2/1024/1024}')

• Perform lvextend on "/dev/vg_alt_root/lv_alt_root"

lvextend -r -l +100%FREE /dev/vg_alt_root/lv_alt_root

• Reboot the appliance using the below command

reboot -f

• Check the status of the appliance in vCenter web console, once up, confirm the available space.

df -h