Log files to monitor during vRealize Automation Upgrade

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

This article is created to educate users on the vRealize Automation upgrade procedure and to list the log files to monitor during the upgrade.

Environment

VMware vRealize Automation 8.x

Resolution

Upgrade Prerequisites:

1. Read release notes 
2. Check Hardware requirements
3. Check the Services status 
4. Ensure backups are done 
5. Ensure a pre-upgrade snapshot is taken

 

Trigger upgrade in vRLCM:

1. Make sure prechecks are successful in vRLCM.  

 

The Upgrade Process explained further:

• Manifest is downloaded (upgrade-noop.log)  
• Searches for the bootstap package and checks if ssh port is open and able to connect (upgrade-datetime.log) 
• Retrieves product version on all nodes 
• Performs Infrastructure health 
• Shuts down Infrastructure and Application services 
• Saves local restore point for k8s processes node data and activates monitor on all nodes 
• Once upgrade monitor is activated on the and cluster nodes are removed successfully, it will proceed for installation.  This takes about 30 minutes. 
• VAMI upgrade starts 
• Download of all packages happens (vami.log)  
• Once downloaded, installation of packages starts (updatecli.log & postupdate.log) 
• Once completed, Appliance is rebooted and VAMI Upgrade is marked successful (upgrade-datetime.log)
• Cluster nodes are added back in and restore points are restored 
• Infrastructure and Application Services are started 
• Upgrade cleanup performed

Log Files to monitor on the vRA appliance during vRA Upgrade process

• /var/log/vmware/prelude/upgrade<<date-time>>.log 
• /var/log/vmware/prelude/upgrade-noop.log
• /opt/vmware/var/log/vami/vami.log
• /var/log/bootstrap/postupdate.log
• /opt/vmware/var/log/vami/updatecli.log