7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message
- 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
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
PostgreSQL External Database Merge Is Unsuccessful
The external PostgreSQL database merge with the embedded PostgreSQL database does not succeed.
Problem
If the external PostgreSQL database version is newer than the embedded PostgreSQL database version, the
merge does not succeed.
Solution
1 Log in to the host for the PostgreSQL external database.
2 Run the psql --version command.
Note the PostgreSQL version for the external database.
3 Log in to the host for the PostgreSQL embedded database.
4 Run the psql --version command.
Note the PostgreSQL version for the embedded database.
If the external PostgreSQL version is newer than the embedded PostgreSQL version, contact support for
assistance to merge your external PostgreSQL database.
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.
Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
62 VMware, Inc.