Aria Automation failing to deploy via Lifecycle Manager with error message "Failed to Set VMware Identity Manager HostName on VMware Aria Automation"
search cancel

Aria Automation failing to deploy via Lifecycle Manager with error message "Failed to Set VMware Identity Manager HostName on VMware Aria Automation"

book

Article ID: 404808

calendar_today

Updated On:

Products

VCF Automation VMware vRealize Suite Lifecycle Manager 8.x

Issue/Introduction

  • Aria Automation fails to deploy via Lifecycle Manager at stage 11 with error message "Failed to Set VMware Identity Manager HostName on VMware Aria Automation"
  • Lifecycle Manager shows error code LCMVRAVACONFIG590008
  • The /var/log/vrlcm/vmware_vrlcm.log on the Lifecycle Manager shows the following error message

2025-07-18T21:15:18.407z INFO vrlcm[1318] [pool-3-thread-21] [c.v.v.l.u.SshUtils] -- Command: vracli vidm set https://aria_automation_hostname admin /tmp/adminpassword.txt YXYXYXYX -f DEFIEA83D231EA3D5gc3FD788649D82AF391D7E 
2025-07-18T21:15:18.407z INFO vrlcm[1318] [pool-3-thread-21] [c.v.v.l.u.SshUtils] -- exit-status: 1 

2025-07-18T21:15:20.700z INFO vrlcm[1318] [pool-3-thread-21] [c.v.v.l.d.v.h.VraPreludeInstallHelper] -- Fetching vIDM certificate info from aria_automation_hostname 

2025-07-18T21:15:22.450z [ERROR] Exception while setting vidm. 
Traceback (most recent call last) : 
File "/opt/python-modules/vracli /commands/vidm. py", line 97, in set _ handler 
if not vidm_obj.get_user(args.user):
File "/opt/python-modules/vracli/vi dm. py", line 112, in get_user 
raise Exception(f"Request for user {username} returned too many results: {len(resources)}") 
Exception: Request for user user_name returned too many results: 2 

Environment

Lifecycle Manager 8.x

Aria Automation 8.x

Cause

This issue occurs when vIDM has two user accounts which match the system domain admin account (such as configadmin) which is trying to perform the vracli vidm set task. For example, this issue will arise if there is a system domain admin account (such as configadmin) and an Active Directory user also named configadmin which is synced within vIDM

Resolution

To resolve this issue you will need to remove the Active Directory user from the domain sync settings which has the same name as the system domain account name. After the Active Directory user has been removed from vIDM you can complete the Aria Automation deployment from Lifecycle Manager