7.4
Table Of Contents
- Upgrading from vRealize Automation 7.1 or Later to 7.4
- Contents
- Upgrading vRealize Automation 7.1, 7.2, or 7.3.x to 7.4
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Run NSX Network and Security Inventory Data Collection Before You Upgrade vRealize Automation
- Backup Prerequisites for Upgrading vRealize Automation
- Back Up Your Existing vRealize Automation Environment
- Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous
- Downloading vRealize Automation Appliance Updates
- Updating the vRealize Automation Appliance and IaaS Components
- Upgrading the IaaS Server Components Separately If the Update Process Fails
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation
- Upgrading Software Agents to TLS 1.2
- Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
- Run Test Connection and Verify Upgraded Endpoints
- Run NSX Network and Security Inventory Data Collection After You Upgrade from vRealize Automation
- Join Replica Appliance to Cluster
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Restore External Workflow Timeout Files
- Enabling the Connect to Remote Console Action for Consumers
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Troubleshooting the vRealize Automation Upgrade
- Automatic Manager Service Failover Does Not Activate
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Delete Orphaned Nodes on vRealize Automation
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- PostgreSQL Database Upgrade Merge Does Not Succeed
- Replica vRealize Automation Appliance Fails to Update
- Backup Copies of .xml Files Cause the System to Time Out
- Exclude Management Agents from Upgrade
- Unable to Create New Directory in vRealize Automation
- vRealize Automation Replica Virtual Appliance Update Times Out
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading to vRealize Automation Fails
- Unable to Update DEM and DEO Components
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- vRealize Automation Update Fails Because of Default Timeout Settings
- Upgrading IaaS in a High Availability Environment Fails
- Work Around Upgrade Problems
Log In Fails After Upgrade
You must exit the browser and log in again after an upgrade for sessions that use unsynchronized user
accounts.
Problem
After you upgrade vRealize Automation, the system denies access to unsynchronized user accounts at
login.
Solution
Exit the browser and relaunch vRealize Automation.
Delete Orphaned Nodes on vRealize Automation
An orphaned node is a duplicate node that is reported on the host but does not exist on the host.
Problem
When you verify that each IaaS and virtual appliance node is in a healthy state, you might discover that a
host has one or more orphaned nodes. You must delete all orphaned nodes.
Solution
1 On your primary vRealize Automation appliance, log in to vRealize Automation Appliance
Management as root using the password you entered when you deployed the vRealize Automation
appliance.
2 Select vRA settings > Cluster.
3 For each orphaned node in the table, click Delete.
Join Cluster Command Appears to Fail After Upgrading a
High-Availability Environment
After you click Join Cluster in the management console on a secondary cluster node, the progress
indicator disappears.
Problem
When you use the vRealize Automation appliance management console after upgrade to join a
secondary cluster node to the primary node, the progress indicator disappears and no error or success
message appears. This behavior is an intermittent problem.
Cause
The progress indicator disappears because some browsers stop waiting for a response from the server.
This behavior does not stop the join cluster process. You can confirm that the join cluster process is
successful by viewing the log file at /var/log/vmware/vcac/vcac-config.log.
Upgrading from vRealize Automation 7.1 or Later to 7.4
VMware, Inc. 66