Patch Installation For Aria Automation Fails With No Errors

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Aria Automation patch installation completes prematurely, and the patched version is not reflected in the environment, despite multiple attempts.

• The following error might also be seen while retrying patch installation after cleaning leftover upgrade data. The following message will be observed in the var/log/vrlcm/vmware_vrlcm.log file:

  • 2025-05-30T03:13:43.133Z ERROR vrlcm[1166] [pool-3-thread-30] [c.v.v.l.p.c.v.t.VraVaUpgradeStatusCheckTask]  -- Un-expected status seen after Upgrade on VMware Aria Automation VA <FQDN>. To know more about the failure, run command "vracli upgrade status --details" on the VMware Aria Automation VA <FQDN>. Upgrade is not successful, VMware Aria Automation appliance has been auto reverted to its previous working state. You can retry the upgrade by going to the product section

• • Error Code: LCMVRAVACONFIG90030
  • 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 <FQDN>. To revert to snapshot, click RETRY with 'revertSnapshot' property set to true.

• The following events will be observed in the /var/log/vmware/prelude/upgrade-noop.log file.

  • [INFO][2025-05-28 23:01:53][<FQDN>] Downloading manifest ...
  • [INFO][2025-05-28 23:01:53][<FQDN>] Manifest downloaded successfully.
  • [INFO][2025-05-28 23:01:53][<FQDN>] Validating manifest ...
  • [ERROR][2025-05-28 23:01:53][<FQDN>][Exit Code: 1] Manifest signature validation failed.
  • [ERROR][2025-05-28 23:01:53][<FQDN>] Repository product ID mismatch. The specified repository is not applicable for this product.
  • [ERROR][2025-05-28 23:01:53][<FQDN>] Manifest validation failed.

Environment

• Aria Automation 8.x

• Aria Suite Lifecycle 8.x

Cause

• The patch installation failure was primarily caused by a corrupted or incorrect patch binary manifest, leading to signature validation and product ID mismatch errors. 

• This issue was compounded by the presence of leftover runtime upgrade files from previous attempts.

Resolution

1. Clean Leftover Upgrade Data: Removed/cleaned old upgrade and patch data from the Aria Automation node (refer to KB 377241 for guidance).

2. Delete Problematic Patch Binary: Deleted the patch from Aria Suite Lifecycle (Lifecycle Operations > Settings > Binary Mapping > Patch Binaries page).

3. Re-add Correct Patch Binary: Re-added the patch binary to LCM (refer to KB 389977 for guidance).

4. Verify Checksum: Verified the consistency of the re-added file by checking its checksum in LCM (refer to KB 286808 for guidance).

5. Re-initiate Patch Installation: Initiated the patch installation again.

Additional Information

• Initially, the LCM Product Patch Install request may complete in an unusually short time (13 minutes 42 seconds), indicating a problem

• Logs (vmware_vrlcm.log and upgrade-noop.log) would show warnings about leftover files, unexpected upgrade status, manifest signature validation failures, and repository product ID mismatches

• The successful resolution after removing and re-adding the patch binary confirms that the integrity and correct mapping of the patch file were crucial for a successful installation

• The patch installation would then complete successfully after approximately an hour, which is the expected duration