Cloud proxy shows up as offline after it fails to upgrade during Aria Operations/VCF Operations cluster upgrade

Products

• VCF Operations

Issue/Introduction

After an Aria operations / VCF Operations upgrade, you notice a cloud proxy is offline.

You notice the version is not in-line with the rest of your cluster. Check the version using:

• cprc-cli -s

Environment

• Aria operations 8.x
• VCF Operations 9.x

Cause

The upgrade has failed on the cloud proxy, leaving it in a failed state.

Resolution

Manually patch the cloud proxy to bring it back in line with the rest of the cluster

1. Log in to the Primary node as root via SSH or Console, pressing ALT+F1 in a Console to log in. 
2. Navigate to the '/storage/db/proxyrc/pak' directory and verify the existence of the '*-Operations-Cloud-Proxy-build_number.pak' file.
3. Log in to the Cloud Proxy as root via SSH or Console, pressing ALT+F1 in a Console to log in.
4. Using an SCP utility, download the '*-Operations-Cloud-Proxy-build_number.pak' file from the Primary node to the /storage/db/tmp directory on the Cloud Proxy.
5. On the Cloud Proxy, run the following command to initiate the upgrade:

   cprc-cli -u *-Operations-Cloud-Proxy-build_number.pak

Note: Replace build_number with the build of the Cloud Proxy upgrade package found on the Primary node.

Example:
cprc-cli -u /storage/db/tmp/*-Operations-Cloud-Proxy-8.18.0.24025142.pak

The upgrade should take about 2 to 5 minutes.  After a successful upgrade, the Cloud Proxy will be restarted.

You can use the 'cprc-cli --status' command to check the version and upgrade status.

If this does not fix the cloud proxy, deploy a new one to replace the broken proxy.

Additional Information

How to manually upgrade a VMware Aria Operations Cloud Proxy via CLI