Patch Installation fails with LCMVRAVACONFIG90030 due to stale Aria Automation upgrade metadata
search cancel

Patch Installation fails with LCMVRAVACONFIG90030 due to stale Aria Automation upgrade metadata

book

Article ID: 398279

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • When attempting to install Patch 2 (vrlcm-vra-8.18.1-8.18.1.36920) for VMware Aria Automation via Aria Suite Lifecycle (vRSLCM), you may encounter the following error shortly after the process begins or the process fails a few seconds into the install:
LCMVRAVACONFIG90030
  • Despite this error, inventory sync between vRSLCM and Aria Automation completes successfully, indicating SSH connectivity is not the issue.
  • You have previously upgraded Aria Automation in this environment from an older version at some point in time with no indication of that upgrade process failing.
    • This means that the Aria Automation product version reflects the expected version you attempted to upgrade to.

Environment

VMware Aria Automation 8.x

VMware Aria Suite Lifecycle 8.x

Cause

The error occurs because the Aria Automation cluster retains stale upgrade metadata from a previously completed upgrade. This causes vracli upgrade status to continue reporting an upgrade as in progress, preventing vRSLCM from re-initiating the patch application and triggering the generic error code LCMVRAVACONFIG90030.

Resolution

Resolution:

To resume and complete the upgrade and allow vRSLCM to function correctly:

  1. SSH into one of the Aria Automation nodes.

  2. Run the following command to resume, then complete the upgrade and clear the internal upgrade lock:

     
    vracli upgrade exec --resume
  3. Monitor the output to confirm that the upgrade process finishes without additional errors.

  4. Once complete, retry the patch installation through the vRSLCM UI.

Note: This issue is commonly seen when the previous upgrade completed successfully but did not clear the upgrade state. Resuming the upgrade from CLI allows the cluster to complete and finalize the state transition.