Troubleshooting VMware Aria Automation 8.x Installations and Day2 operations
Article ID: 326148
Updated On:
Products
Issue/Introduction
Symptoms:
The following VMware Aria Automation 8.x (formerly vRealize Automation 8.x) and VMware Aria Suite Lifecycle 8.x (formerly vRealize Suite Lifecycle Manager 8.x) functions are impacted:
- Installation
- Import Brownfield
- Scale out
- Replace Certificate
Environment
VMware Aria Automation 8.x
VMware vRealize Automation 8.x
VMware vRealize Suite Lifecycle Manager 8.x
Resolution
Problem: vRealize Automation (vRA) 8.0 highly available (HA) "Initialize Cluster" fails with a misconfigured Load Balancer.
Workaround: Ensure the Load Balancer has been configured correctly, then, retrigger the deployment.
Problem: vRealize Automation 8.0 HA deployment "Initialize Cluster" stage fails when SSL pass through is not enabled within the defined NSX Load Balancer.
Workaround: Enable SSL passthrough on the NSX Load Balancer before retriggering the deployment.
Problem: vRealize Automation 8.0 deployment fails intermittently at the "Initialize Cluster" stage reporting the failure within the Easy Installer.
Workaround: Please retry the failed vRealize Automation deployment request from the "Requests" tab by logging into the vRealize Suite Lifecycle Manager UI.
Problem: vRealize Automation 8.0 highly available (HA) deployment "Initialize Cluster" stage fails when the provided SAN certificate does not contain all four hostnames.
Workaround: Please ensure to provide all four hostnames within the subjectAltName attribute of the custom certificate. This will include the 3 vRealize Automation virtual appliances and the Load Balancing virtual IP hostname.
Problem: vRealize Automation 8.0 highly available (HA) deployment "Initialize Cluster" stage fails when a wildcard certificate is used for the deployment.
Workaround: Please ensure to provide all four hostnames within the subjectAltName attribute of the custom certificate. Certificates in which only have a wildcard entry within the CN will not work. See https://www.digicert.com/kb/ssl-support/wildcard-san-names.htm for additional information on wildcards within SAN fields.
Problem: vRealize Automation 8.0 "Scale out" from a single node to three node HA cluster fails at the "Initialize Cluster" stage sometimes due to liquibase locks.
Workaround: Click the retry option to reattempt the scale out during the initialize cluster stage.
Problem: vRealize Automation 8.0 "Import Brownfield" environment fails when VMware Identity Manager present within vRealize Suite Lifecycle Manager 8.0 does not match the VMware Identity Manager registered with vRealize Automation.
Workaround: Please ensure the VMware Identity Manager present within vRealize Suite Lifecycle Manager is the same as the VMware Identity Manager registered with vRealize Automation and then reattempt the "Import Brownfield" function.
Problem: vRealize Automation 8.0 "Import Brownfield" fails when VMware Identity Manager default configuration admin present within vRealize Suite Lifecycle Manager does not match with the vRealize Automation vIDM default configuration admin user.
Workaround: Please ensure the same configuration admin user is used for both VMware Identity Manager and vRealize Automation within LCM.
Problem: vRealize Automation 8.0 "Replace certificate" fails intermittently during the "Initialize Cluster" stage after replacing the certificate.
Workaround: Please retry the failed replace certificate request to clear the cluster initialization.
Problem: vRealize Automation 8.0 HA "Replace certificate" fails at "Initialize Cluster" after replacing the existing certificate with a SAN certificate that contains more than the required hostnames in the environment.
Workaround: Ensure the SAN certificate to be applied contains only the hostnames of the required nodes participating in the environment: 3 virtual appliance nodes and 1 virtual IP representing the load balancing address.
Feedback
