7.2
Table Of Contents
- Upgrading from vRealize Automation 7.1 to 7.2
- Contents
- Updated Information
- vRealize Automation 7.1 Upgrade Prerequisites and Process
- Preparing to Upgrade vRealize Automation 7.1
- Updating the vRealize Automation 7.1 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 7.1 to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 7.1 to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 7.1
- Troubleshooting the vRealize Automation 7.1 Upgrade
- 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
- Unable to Upgrade Management Agent
- 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
- Management Agent Upgrade is Unsuccessful
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- 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
- Index
4 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 intermient 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 conrm that the join cluster process is successful by
viewing the log le at /var/log/vmware/vcac/vcac-config.log.
PostgreSQL Database Upgrade Merge Does Not Succeed
The external PostgreSQL database merge with the embedded PostgreSQL database does not succeed.
Problem
If the PostgreSQL database upgrade merge does not succeed, you can perform a manual merge.
Solution
1 Revert the vRealize Automation virtual appliance to the snapshot you made before upgrade.
2 Log in to the vRealize Automation virtual appliance and run this command to allow upgrade to
complete if the database merge does not succeed.
touch /tmp/allow-external-db
The command does not disable auto merge.
3 On the remote PostgreSQL database host, connect to the PostgreSQL database using the psql tool and
run these commands.
CREATE EXTENSION IF NOT EXISTS "hstore";
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
CREATE SCHEMA saas AUTHORIZATION vcac;
The user in this command is vcac. If vRealize Automation connects to the external database with a
dierent user, replace vcac in this command with the name of that user.
CREATE EXTENSION IF NOT EXISTS "citext" SCHEMA saas;
4 Run upgrade.
If upgrade is successful, the system works as expected with the external PostgreSQL database. Ensure
that the external PostgreSQL database is running properly.
5 Log in to the vRealize Automation virtual appliance and run these commands
/etc/bootstrap/postupdate.d/00-20-db-merge-external
/etc/bootstrap/postupdate.d/11-db-merge-external
Chapter 9 Troubleshooting the vRealize Automation 7.1 Upgrade
VMware, Inc. 43