Pod status of Pending or Evicted in vRealize Automation 8.X
book
Article ID: 314809
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms: Running "kubectl get pods -n prelude" command shows Pods are in either a pending or evicted state like the following:
NAME READY STATUS RESTARTS AGE vco-app 0/2 Pending 0 10s
NAME READY STATUS RESTARTS AGE vco-app 0/2 Evicted 0 10s
Environment
VMware vRealize Automation 8.x
Cause
The Kubernetes Evicted state indicates that there is a lack of resources available.
Resolution
Before proceeding with the below steps best practise dictates you first follow the documented clean shutdown and backup procedure in the vRA 8 documentation
SSH to the vRA appliance.
Check the Storage available on the appliance using the vracli disk-mgr command.
If the /data partition is above 80% utilization then you will need to increase the storage on the data partition.
Check the Memory usage using either the top command or the free command with the -m flag.
Based on the output of the above checks either increase the Storage or Memory of the appliance.
To increase the storage:
To increase the vRealize Automation root partition disk to meet the above requirements, increase the vRealize Automation VM "Hard Disk 1" (/dev/sda4) size to the desired GB amount WITHOUT POWERING OFF THE VA in the vCenter server. Then, run the command “vracli disk-mgr resize” on the vRealize Automation VA from the command shell. Disk resize should be reflected within a few minutes.
To increase the vRealize Automation data partition disk to satisfy above requirements, increase the vRealize Automation VM "Hard Disk 2" (/dev/mapper/data_vg-data) size то the desired GB amount WITHOUT POWERING OFF THE VA in the vCenter Server. Then, run the command “vracli disk-mgr resize” on the vRealize Automation VA from the command shell. Disk resize should be reflected within few minutes.