Error LCMVRAVACONFIG900309 is seen during Upgrade/Patch due to Timeout on Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to apply a patch or upgrade to VMware Aria Automation from VMware Aria Suite Lifecycle, the request fails in the Lifecycle Manager UI after approximately 4 hours.

Error Code: LCMVRAVACONFIG900309

Error Message:

VMware Aria Automation VA Upgrade Status Check failed.
Upgrade on vRealize Automation VA [FQDN] failed with state 'fatal'. To know more about the failure, run command 'vracli upgrade status --details' on the vRealize Automation VA.

Environment

Aria Suite Lifecycle Manager 8.18.x

Aria Automation 8.18.x

Cause

The Aria Suite Lifecycle manager has a hard-coded timeout period of 4 hours for the upgrade status check task.

In some environments—due to resource constraints, large database sizes the Aria Automation appliance may require more than 4 hours to complete the upgrade scripts. If the process exceeds this window, Aria Suite Lifecycle Manager marks the task as failed even though the upgrade process continues to run successfully in the background on the Aria Automation appliances.

Resolution

To resolve this issue, follow the action plan outlined below:

Verify Upgrade Status via CLI:

1. SSH into the Aria Automation node identified in the error message as root.
2. Execute the below command:

   vracli upgrade status --details

3. If the output shows that the upgrade is still "in progress":

   • We can either wait for it to finish

     • OR

   • Please contact technical support and note this KB in the problem description. For more information, see How to Submit a Support Request.
4. If the output shows "Result: upgraded" proceed to the next step.

Sync Inventory in Aria Suite Lifecycle:

Once the CLI confirms the upgrade is complete, you must synchronize the state with Lifecycle Manager to clear the failure.

1. Navigate to Aria Suite Lifecycle UI.

2. Go to Environments > [Your Environment] > Aria Automation.

3. Click on Trigger Inventory Sync.

4. Once the sync is finished, verify that the Aria Automation version reflects the new patch level.

Additional Information

Note: If the patch history under vRSLCM > Environments > [Environment Name] > Day 2 Tasks > Patches > Patch History does not reflect the current patch level, follow the steps below to synchronize the metadata:

1. Clear existing patch/upgrade data: Remove outdated 'upgrade or patch' data from the Aria Automation nodes by following KB: 383108.
2. Clear previous patch/upgrade request in LCM: Remove prior tasks from vRSLCM using KB: 322700.
3. Reboot: Restart the vRSLCM appliance.
4. Snapshots: Take snapshots of the vRSLCM appliance and all Aria Automation nodes.
5. Re-apply Patch: Re-initiate the patch installation from vRSLCM.
6. Validation: vRSLCM will detect the existing patch on the appliances and update its internal database to reflect the correct patch history without reinstalling binaries.

Technical Impact:

• This procedure is non-disruptive. It does not bring Aria Automation services offline and only reconciles the vRSLCM database with the actual state of the environment.