How to re-trigger a failed VCF Automation 9.0 upgrade

Products

• VCF Automation

Issue/Introduction

This document outlines the steps needed to re-trigger from scratch a failed VCF Automation 9.0 upgrade. 

Environment

VCF Automation 9.0
VMware Aria Automation  8.18.0

Resolution

When importing VMware Aria Automation 8.x into VCF Operations 9.x for an upgrade, this Automation 8.x is removed from the source VMware Aria Suite Lifecycle.

Resolution Steps:

• Delete the failed Automation instance from VCF Operations 9.x
• Log in to vCenter, power on all VMware Aria Automation appliances, and wait for them to start. These appliances should have been shut down gracefully as part of a previous upgrade attempt
• Log in to the console of any appliance and run the following command to restore the services on all nodes:

# /opt/scripts/deploy.sh

Verify that all services are up and running by executing the following command:

# kubectl get pods -A

• Re-import VMware Aria Automation 8.x into VCF Operations 9.0
• Once the import of VMware Aria Automation 8.x into VMware Aria Suite Lifecycle 8.x is complete, launch VCF Operations 9.0 and then import VMware Aria Automation 8.x again to trigger the upgrade