Upgrading to VMware Aria Automation 8.18.1 might result in an error code LCMVRAVACONFIG90030 from Aria Lifecycle Manager

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Attempting to upgrade VMware Aria Automation from version 8.1X.X to 8.18.1 in a clustered environment via VMware Aria Suite Lifecycle (LCM) results in failure during Stage-2 with the following error: LCMVRAVACONFIG90030
• The upgrade process stops at the "VMware Aria Automation Upgrade Status Check failed." stage, and the environment remains in a failed state.
   
• Detailed Error Logs:
  • From LCM UI:
    • • Error Code: LCMVRAVACONFIG90030
      • VMware Aria Automation VA Upgrade Status Check failed.
      • Upgrade on vRealize Automation VA <FQDN> failed with state 'fatal'. Un-expected status in upgrade status check response. To know more about the failure, run command 'vracli upgrade status --details' on the VMware Aria Automation VA <FQDN>."
  • From /var/log/vmware/prelude/upgrade-error-XXXXX.log OR 'vracli upgrade status --details':
    • [ERROR][TS][FQDN] No running application services are found. Application services are expected to run.
      [ERROR][TS][FQDN] Services verification found errors.

Environment

• VMware Aria Automation 8.x
• VMware Aria Suite Lifecycle 8.x

Cause

• The upgrade process failed during the services verification step because the Aria Automation pods were not in the required Running state.
• A subsequent investigation using the command 'kubectl get pods -n prelude -o wide' revealed that the pods could not be found. This suggests that they may have been deleted, failed to deploy, or never initialized. This absence of the required pods led to the upgrade script reporting errors and halting the upgrade process.

Resolution

1. Verify the status of the pods in the Aria Automation Appliance.

          Run the following command to check if the pods are not in a running state:

kubectl get pods -n prelude

2. Use the RETRY button in the LCM Upgrade Request UI to revert to a healthy snapshot, setting the 'revertSnapshot' property to true.
3. Before starting the upgrade, make sure all the pods are up and running using the following command:

kubectl get pods -n prelude

      4. If all the pods are running, trigger an inventory sync and retry the upgrade from LCM.

The upgrade of Aria Automation should now complete successfully and be marked as complete in Aria Suite Lifecycle Manager.