Error Code: LCMVRAVACONFIG590008 when re-trusting Aria Automation with VMware Identity Manager on Aria Lifecycle Manager

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When re-trusting Aria Automation with VIDM on Aria Suite Lifecycle Manager, the task fails with:

Error Code: LCMVRAVACONFIG590008
Failed to Set VMware Identity Manager HostName on VMware Aria Automation.
Failed to set vIDM Host on VMware Aria Automation VA : VIDM's-LB-Address

com.vmware.vrealize.lcm.common.exception.EngineException: Failed to set vIDM Host on VMware Aria Automation VA : VIDM's-LB-Address
	at com.vmware.vrealize.lcm.plugin.core.vra80.task.VraVaSetVidmTask.execute(VraVaSetVidmTask.java:82)
	at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

• Both VIDM and Aria Automation are up and login is successful 
• Inventory sync for Aria Automation is successful 
• Re-trust of VIDM with any other product, like Aria Operations, completes without failure 

Environment

VMware Aria Suite Lifecycle Manager 8.18.x 

Cause

The task for re-trust VIDM with VRA is running against VIDM's Load Balancer FQDN. 

Resolution

To resolve the issue, follow the below steps:

1. When the re-trust VIDM with Aria Automation request fails on Lifecycle Manager, click on Retry option under the error message. 
   
   
   
   
2. In the hostname field, remove the VIDM's Load Balancer Address and input the Primary node's IP/FQDN
3. Submit the request again 
4. The request should complete successfully this time