Skip to main content

 Re-trust between Aria Automation and IDM failed

https://knowledge.broadcom.com/external/article?articleNumber=388670

Products

VMware Aria Suite

Issue/Introduction

When running the Re-Trust with Identity Manager task against Aria Automation, you get this error:

Error Code: LCMVRAVACONFIG590062
Failed to check VMware Identity Manager root certificate on VMware Aria Automation. Check VMware Aria Suite Lifecycle logs for more details

Environment

Aria Automation 8.x (vRA 8.x) 
Aria Suite Lifecycle 8.x (LCM 8.x)

Cause

Root password is expired on Aria Automation nodes

Resolution

Update the password in the appliances and add the new password to the Aria Lifecycle Locker: 

  1. Log into the Aria Automation Appliance(s) and change the password when prompted. 
  2. Create a new Locker Password in Aria Lifecycle under Locker > Passwords > Add
  3. After the new password is created in the Locker, you can sync the password by retrying the failed Re-Trust task and select the new Password entry.
         Note: The task will fail for each node and will need to be retried with the new password selected for each. Once it succeeds, the password will be synced in Lifecycle Manager. 

Alternatively, if you do not wish to retry the failed task but wish to sync the new Aria Automation root password to Lifecycle Manager, you can sync the password in Lifecycle manager by creating the Password entry in the Locker for the new root password and then Changing the password for each node. 

  1. Go to Lifecycle Operations > Environments > Your Automation Environment (View Details) > VMware Aria Automation Nodes > Change Node Password
  2. Select the Current Password (the one configured before changing)
  3. Select the new password (the one that was set via SSH when prompted)
  4. Submit
  5. Repeat for the remaining nodes if applicable. 

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more