Considerations for configuring vRealize Automation

Consider the following information when performing scale-out, deployment, replace certificate, and import brownfield operations in vRealize Suite Lifecycle Manager.

• When the vRealize Automation replace certificate fails intermittently at initialize cluster after replacing the certificate, retry the failed vRealize Automation replace certificate.
• vRealize Automation HA replace certificate fails at the initial cluster after replacing the certificate, when SAN certificate has additional host names. At this instance, replace the vRealize Automation HA certificate with SAN certificate which has the required hostnames like vRealize Automation load balancer host name and three vRealize Automation hostnames.
• When vRealize Automation scale out fails at initialize cluster due to liquibase locks then click the retry option in the failed vRealize Automation scale out request to retry the initialize cluster step.
• Verify if the SAN certificate is used instead of wild card certificate for vRealize Automation deployment.
• Verify to provide all four host names, including three vRealize Automation node host names and a vRealize Automation load balancer host name in the SAN certificate when the custom certificate is used.