Upgrading Aria Automation to 8.x Fails with Error Code LCMVRAVACONFIG90030 or LCMVRAVACONFIG90029 in Aria Lifecycle Manager

Products

• VMware Aria Suite

Issue/Introduction

When attempting to upgrade Aria Automation to version 8.x through Aria Lifecycle Manager, the process fails with the error code LCMVRAVACONFIG90030 or LCMVRAVACONFIG90029, indicating a "VMware Aria Automation VA Upgrade Status Check Failed."

The following error is recorded in the log file /var/log/vmware/prelude/upgrade-noop.log:

[INFO][2024-10-01 14:13:36][vRA_Hostname] Downloading manifest …
[ERROR][2024-10-01 14:15:47][vRA_Hostname][Exit Code: 28] File manifest/manifest-latest.xml is not available in the repository.
[ERROR][2024-10-01 14:17:58][vRA_Hostname][Exit Code: 28] File manifest/manifest-latest.xml.sig is not available in the repository.
[ERROR][2024-10-01 14:17:58][vRA_Hostname] Manifest cannot be downloaded from the repository.

Environment

Aria Automation 8.x

Cause

The error is due to the Aria Automation node being unable to access the product binary repository hosted by Aria Lifecycle Manager. This may be because:

• The repository is not exposed correctly in vrlcm.
• Network connectivity issues between the Aria Automation node and Aria Life Cycle Manager.
• Missing or inaccessible manifest files in the Aria Life Cycle Manager repository.

Resolution

1. Restore to Snapshot:

Before making any changes, ensure that Aria Automation is restored to a previous operational state by verifying the services.

vracli service status
kubectl get pods -n prelude

2. Check Connectivity to LCM:

SSH into the Aria Automation node and run the following curl commands to verify connectivity to Life Cycle Manager node:

curl -kv https://<LCM_Hostname>:443/
curl -kv https://<LCM_Hostname>/repo/productBinariesRepo/vra/8.xx.x/upgrade/update/manifest/manifest-latest.xml

Note: replace the version you're trying to upgrade in place of 8.x.x in the above command. 

Expected Result:

• The first command should return HTTP 200, indicating a successful connection to LCM.
• The second command should also return HTTP 200 if the manifest file is accessible.
• If the second command returns HTTP 404, the binary repository is not properly exposed.

Expose the Binary Repository:

If the manifest file cannot be downloaded, go into the Aria Life Cycle Manager UI and delete and re-add the product binary mapping for the vRA upgrade.
Reference the Configure product binaries section in LCM documentation for guidance on properly mapping the binaries.

Re-run Curl Commands:

After reconfiguring the binary mapping, re-run the curl commands mentioned in step-1. Both commands should return HTTP 200.
Only proceed with the upgrade after ensuring that both curl commands succeed. If the manifest files remain inaccessible, the upgrade will continue to fail.