Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Troubleshooting VMware Aria Automation 8.x Installations and Day2 operations (76532)

Last Updated: 9/19/2023Categories: TroubleshootingTotal Views: 12823Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

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

Purpose

Detail and describe the known issues and troubleshooting steps for a VMware Aria Automation 8.x Installation and VMware Aria Suite Lifecycle 8.x Day 2 operations such as Import Brownfield, Scale out, and Replace Certificate.

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Suite Lifecycle

VMware Aria Automation

Related Versions:

VMware vRealize Suite Lifecycle Manager 8.x

VMware vRealize Automation 8.x

VMware Aria Suite Lifecycle 8.x

VMware Aria Automation 8.x

Take Our Survey

Support Assistant