Aria Automation reconfiguration fails after redeploying VMware Identity Manager as a single node
search cancel

Aria Automation reconfiguration fails after redeploying VMware Identity Manager as a single node

book

Article ID: 452555

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When replacing a VMware Identity Manager (vIDM) cluster with a new single-node appliance, VMware Aria Automation fails to reconfigure with the new instance. This is typically observed when the environment is moving from a VIP address FQDN to a single node FQDN.

During the reconfiguration process, the /opt/scripts/vidm_recovery.py script fails with invalid username and password errors. This occurs despite being able to successfully log into the vIDM UI with the new accounts. Additionally, running vracli vidm apply fails to execute any changes.

Environment

VMware Aria Automation 8.18.x

VMware Identity Manager 3.3.7

Cause

This issue occurs when the configadmin user is missing from the user_org and user_role database tables, meaning the identity service does not recognize it as an org_owner. Furthermore, the presence of legacy users retaining the org_owner role prevents vracli commands from executing. The scripts verify that no current org_owner exists before applying new configurations.

Resolution

This procedure requires manual modifications to the database and is prone to human error.

Contact Broadcom Support with a new case requesting assistance.