Replacing Certificate Request for vIDM fails with LCMVRAVACONFIG590003 during Cluster Initialization Step for Aria Automation
Article ID: 425556
Updated On:
Products
Issue/Introduction
Error Code: LCMVRAVACONFIG590003Cluster initialization failed on VMware Aria Automation.VMware Aria Automation virtual appliance initialization failed on <nodefqdn>. Login to VMware Aria Automation and check /var/log/deploy.log file for more information about the failure. If it is a VMware Aria Automation high availability and the load balancer has to be reset, set the 'isLBRetry' to 'true' and enter a valid load balancer hostname.
Environment
Aria Suite Lifecycle 8.18.5
Aria Automation 8.18.x
VMware Identity Manger 3.3.7
Cause
This error message is usually caused when the services fail to start on the Aria Automation nodes. The root cause can vary.
Resolution
This can sometimes be caused by a transient state, and reviewing the /var/log/deploy.log shows that the service failed to start for no apparent reason.
If this happens during a vIDM Replace Certificate Request, and examining the deploy.log shows no explicit reason for the failure just after starting the vmware-identity pods, and pods just shows that everything but the basic pods are not running (kubectl get pods -n prelude), then you may be able to retry the operation with success.
- After clicking RETRY a menu with parameters will be displayed.
- Set the isLBRetry to true
- Set the vidm trust recheck to true.
- Validate that the VMware Identity Manager Primary Node shows what is defined in the globalenvironment under vIDM>VMware Identity Manager>VMware Identity Manager Primary Node.
- Validate that the vRA ha VIP fqdn is correct.
Proceed with the retry.
If the issue persists, please see the additional info section for other articles which may provide more clues as to why this may be failing.
Additional Information
Feedback
