Patch operation via Aria Suite Lifecycle shows successful status, but Aria Automation does not update

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When applying Patch 2 (or similar patches) to VMware Aria Automation via Aria Suite Lifecycle (vRSLCM), the patch request completes in approximately 13 - 15 minutes and shows a successful status in the Lifecycle Manager UI. However, the Aria Automation environment remains unchanged and is not actually updated.

Environment

VMware Aria Automation 8.18.x

VMware Aria Suite Lifecycle 8.x

Cause

Aria Automation relies on the LCM FQDN defined during deployment (vralcm.<domain>) to access patch artifacts like manifest-latest.xml. If this hostname is not resolvable due to missing DNS entries, attempts to retrieve patch metadata will fail with curl exit code 6, and the file cannot be downloaded.

Lifecycle Manager can only validate the installation process of the upgrade or patch through its interpretation of the response provided by the vracli upgrade status command. In this scenario, the upgrade status command continues to return a no upgrade in progress which tricks the LCM request into believing the requested operation has completed.

Resolution

1. Confirm LCM System Hostname.
   In Aria Suite Lifecycle:
   • Go to Settings > System Settings
   • Note the configured hostname (e.g., `vralcm.<domain>`)
2. Validate DNS Resolution:
   On the Aria Automation appliance, run:
   • nslookup vralcm.<domain>
   • curl -v http://vralcm.<domain>:8008/repository/manifest/manifest-latest.xml
3. Retry the patch installation request against Aria Automation using Aria Suite Lifecycle.

Additional Information

Patch validation must be confirmed from within Aria Automation if errors or inconsistencies are encountered. Follow the guidance contained within Troubleshooting VMware Aria Automation 8.x (formerly vRealize Automation 8.x) upgrades under the section Upgrade Process Breakdown to further isolate the root cause.