Skip to main content

 

Troubleshooting VMware Aria Automation 8.x (formerly vRealize Automation 8.x) upgrades


Issue/Introduction

  • This article provides steps to manually collect upgrade logs if the log bundle collection fails when a VMware Aria Automation upgrade fails.
  • When an upgrade fails, the following logs need to be analyzed:
/var/log/vmware/prelude/upgrade-*.logUpgrade reports. Review based
on timestamp

One node environment
/opt/vmware/var/log/vami/*.log

Cluster environments
/opt/log/vmware/var/log/vami/*.log

Packages installation details
/var/log/bootstrap/postupdate.logInitialization scripts details
/var/log/bootstrap/everyboot.logInitialization scripts details
/var/log/vmware/prelude/deploy-*.logServices startup details


Note: Some log files will have timestamps as part of the file name, for others the information is appended. It is important to validate that the information is from the latest upgrade attempt.

Overview

Upgrade Prerequisites

  1. Read the product release notes.
  2. Check Hardware requirements.
  3. Check the Services status.
  4. Ensure backups are available.
  5. Ensure a pre-upgrade snapshot is taken.

Trigger upgrade in Aria Suite Lifecycle

  1. Validate prechecks are successful.  

Upgrade Process Breakdown

  • Manifest is downloaded (upgrade-noop.log)  
  • Searches for the bootstap package and checks if ssh port is open and able to connect (update-datetime.log) 
  • Retrieves product version on all nodes
  • Performs Infrastructure health
  • Shuts down Infrastructure and Application services
  • Saves local restore point for k8s processes node data and activates monitor on all nodes
  • Once upgrade monitor is activated and the cluster nodes are removed successfully, it will proceed for installation.  This takes about 30 minutes. 
  • VAMI upgrade starts
  • Download of all packages happens (vami.log)
  • Once down, installation of packages starts (updatecli.log & postupdate.log)
  • Once completed, Appliance is rebooted and VAMI Upgrade is marked successful (update-datetime.log)
  • Cluster nodes are added back in and restore points are restored
  • Infrastructure and Application Services are started
  • Upgrade cleanup performed



Environment

VMware vRealize Automation 8.x
VMware Aria Automation 8.x

Resolution

Manually collecting upgrade failure diagnostic information

  1. SSH to the VMware Aria Automation node indicated in the Aria Suite Lifecycle error.

  2. Validate that there is available disk space in the root partition (/dev/sda4) running the command vracli disk-mgr

    root@vranode1 [ /tmp ]# vracli disk-mgr
/dev/sda4(/):
        Total size: 47.80GiB
        Free: 33.58GiB(70.2%)
        Available(for non-superusers): 31.13GiB(65.1%)
        SCSI ID: (0:0)
/dev/sdb(/data):
        Total size: 140.68GiB
        Free: 109.54GiB(77.9%)
        Available(for non-superusers): 102.32GiB(72.7%)
        SCSI ID: (0:1)
/dev/sdc(/var/log):
        Total size: 21.48GiB
        Free: 9.09GiB(42.3%)
        Available(for non-superusers): 7.97GiB(37.1%)
        SCSI ID: (0:2)
/dev/sdd(/home):
        Total size: 29.36GiB
        Free: 27.41GiB(93.4%)
        Available(for non-superusers): 25.90GiB(88.2%)
        SCSI ID: (0:3)

  3. Run the following command to collect the directories and logs related to the upgrade:

    mkdir /tmp/upgradelogs && cp -R /var/log/vmware/prelude /tmp/upgradelogs && cp -R /opt/vmware/var/log/vami /tmp/upgradelogs && cp -R /var/log/bootstrap /tmp/upgradelogs && tar -zcvf /tmp/upgradelogs.tar.gz /tmp/upgradelogs

  4. Extract and continue the review with the collected file /tmp/upgradelogs.tar.gz  for the failure code or submit this data to Global Services for additional assistance in troubleshooting the upgrade.

  5. After extracting the file from the appliance, remove the file and directory to save disk space:
cd / tmp
rm upgradelogs.tar.gz
rm -r upgradelogs

Additional Information

Labels:

Comments

Post a Comment

Popular posts from this blog

  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

57 Tips Every Admin Should Know

Active Directory 1. To quickly list all the groups in your domain, with members, run this command: dsquery group -limit 0 | dsget group -members –expand 2. To find all users whose accounts are set to have a non-expiring password, run this command: dsquery * domainroot -filter “(&(objectcategory=person)(objectclass=user)(lockoutTime=*))” -limit 0 3. To list all the FSMO role holders in your forest, run this command: netdom query fsmo 4. To refresh group policy settings, run this command: gpupdate 5. To check Active Directory replication on a domain controller, run this command: repadmin /replsummary 6. To force replication from a domain controller without having to go through to Active Directory Sites and Services, run this command: repadmin /syncall 7. To see what server authenticated you (or if you logged on with cached credentials) you can run either of these commands: set l echo %logonserver% 8. To see what account you are logged on as, run this command: ...
Post a Comment
Read more
  The Guardrails of Automation VMware Cloud Foundation (VCF) 9.0 has redefined private cloud automation. With full-stack automation powered by Ansible and orchestrated through vRealize Orchestrator (vRO), and version-controlled deployments driven by GitOps and CI/CD pipelines, teams can build infrastructure faster than ever. But automation without guardrails is a recipe for risk Enter RBAC and policy enforcement. This third and final installment in our automation series focuses on how to secure and govern multi-tenant environments in VCF 9.0 with role-based access control (RBAC) and layered identity management. VCF’s IAM Foundation VCF 9.x integrates tightly with enterprise identity providers, enabling organizations to define and assign roles using existing Active Directory (AD) groups. With its persona-based access model, administrators can enforce strict boundaries across compute, storage, and networking resources: Personas : Global Admin, Tenant Admin, Contributor, Viewer Projec...
Post a Comment
Read more