Inventory sync of VMware Aria Automation Orchestrator 8.x (Formerly called vRealize Orchestrator) in Aria Suite Lifecycle fails with Error Code: LCMVRAVACONFIG590049
search cancel

Inventory sync of VMware Aria Automation Orchestrator 8.x (Formerly called vRealize Orchestrator) in Aria Suite Lifecycle fails with Error Code: LCMVRAVACONFIG590049

book

Article ID: 386486

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

You are running a inventory sync of VMware Aria Automation Orchestrator 8.x in Aria Suite Lifecycle and run into an error 

Error Code: LCMVRAVACONFIG590049
VMware Aria Automation endpoint operation failed. Unable to get VMware Aria Automation authentication token, ensure the credentials are correct and host is reachable.
Exception occurred while validating the VMware Aria Automation host details. Exception message: Could not get VMware Aria Automation token for host: [email protected] username: administrator. Unable to get access token.

Symptoms :

  • In your environment you have setup a Load balancer for a single node Automation and pointed it to a VIP address. This VIP address is different from the Automation node hostname
  • You have a CNAME setup which redirects Orchestrator hostname to a load balancer address

Environment

VMware Aria Automation Orchestrator 8.x

Cause

The root cause of this issue is a misconfigured Load balancer at the Aria Automation end. The Load balancer is incorrectly configured to point to a Virtual IP (VIP) address instead of the actual Automation node hostname. This misconfiguration can lead to authentication failures and prevent Aria Suite Lifecycle from communicating with the Orchestrator instance.

 

Resolution

 

  • Modify the configuration in Aria Automation: Change the Load balancer configuration to point directly to the Single node hostname using vracli load-balancer set xxxx
  • Restart the services: Run /opt/script/deploy.sh and wait for services to restart. 
  • Retest the inventory sync: After making the configuration change, attempt to run the VRO inventory sync from VRSLCM again.

 

Additional Information