Inventory Sync After Aria Automation Upgrade Shows Pre-Upgrade Versions
search cancel

Inventory Sync After Aria Automation Upgrade Shows Pre-Upgrade Versions

book

Article ID: 399976

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

  • Aria Automation upgrade request completes successfully in Aria Suite Lifecycle, but Aria Automation login page page still shows pre-upgrade version.
  • Running "vracli version" command on Aria Automation appliance shows pre-upgrade version.
  • Inventory sync of Aria Automation appliance in Aria Suite Lifecycle updates the product version back to pre-upgrade version
  • The following error is recorded in the log file /var/log/vmware/prelude/upgrade-noop.log in Aria Automation appliance:

[INFO][YYYY-MM-DD HH:MM:SS][Aria Automation node FQDN] Downloading manifest ...
[ERROR][YYYY-MM-DD HH:MM:SS][Aria Automation node FQDN][Exit Code: 3] File manifest/manifest-latest.xml is not available in the repository.
[ERROR][YYYY-MM-DD HH:MM:SS][Aria Automation node FQDN][Exit Code: 3] File manifest/manifest-latest.xml.sig is not available in the repository.
[ERROR][YYYY-MM-DD HH:MM:SS][Aria Automation node FQDN] Manifest cannot be downloaded from the repository.

  • The repository type used in the Aria Automation upgrade request in Aria Suite Lifecycle is "Repository URL".

 

 

 

Environment

Aria Automation 8.x

Cause

Typically, this issue can occur when an incorrect Repository URL is provided. Repository URL used in the request can be validated by reviewing the log file /var/log/vrlcm/vmware_vrlcm.log in Aria Suite Lifecycle for below log entries :

YYYY-MM-DDTHH:MM:SS.xxxZ INFO vrlcm[1258] [pool-3-thread-40] [c.v.v.l.d.v.h.VraPreludeInstallHelper]  -- PRELUDE ENDPOINT HOST :: <Aria Automation Node FQDN>
YYYY-MM-DDTHH:MM:SS.xxxZINFO vrlcm[1258] [pool-3-thread-40] [c.v.v.l.d.v.h.VraPreludeInstallHelper]  -- COMMAND :: vracli upgrade exec --check --json --profile lcm --repo '<REPO_PATH>'

The REPO_PATH must be a valid Repository URL accessible from Aria Suite Lifecycle and must contain the upgrade ISO file of Aria Automation appliance.

Resolution

1. Revert back the appliance to the pre-upgrade snapshot.

2. Power On the Aria Automation appliance from Aria Suite Lifecycle

3. Follow the procedure mentioned in document Upgrade vRealize Automation 8.x or VMware Aria Automation by using VMware Aria Suite Lifecycle . Verify that the Repository URL is valid and contains the Update Repository ISO file for Aria Automation upgrade. Alternatively, the upgrade can be performed using VMware Aria Suite Lifecycle Repository, by adding the binary mapping of the VMware Aria Automation upgrade ISO priorly.