Upgrade Prerequisites:
- Read release notes
- Check Hardware requirements
- Check the Services status
- Ensure backups are done
- Ensure a pre-upgrade snapshot is taken
Trigger upgrade in vRLCM:
- 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 (update-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 down, installation of packages starts (updatecli.log & postupdate.log)
- Once completed, Appliance is rebooted and VAMI Upgrade is marked successful (update-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