7.2
Table Of Contents
- Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
- Contents
- Updated Information
- vRealize Automation 7.0 or 7.0.1 Upgrade Prerequisites and Process
- Preparing to Upgrade vRealize Automation 7.0 or 7.0.1
- Updating the vRealize Automation 7.0 or 7.0.1 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 7.0 or 7.0.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.0 or 7.0.1
- Troubleshooting the vRealize Automation 7.0 or 7.0.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
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
- IaaS Windows Services Fail to Stop
- PostgreSQL External Database Merge Is Unsuccessful
- Delete Orphaned Nodes on vRealize Automation
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Management Agent Upgrade is Unsuccessful
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- 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
e Select the script action.
f Click OK.
g Congure the Input Parameters that are included in the script action. To preserve the existing
relationship, bind the parameter to the other property.
h Click OK.
IaaS Windows Services Fail to Stop
An error message about Windows services appears when you click Install Updates on the
VMware vRealize ™ Automation management console Update Status page.
Problem
Upgrade process appears to be unsuccessful. Message appears: Failed to stop service service name.
Cause
The IaaS Manager Service does not stop because the Windows service stop process times out. Because a
running IaaS Manager Service does not block the upgrade, the message can be safely ignored.
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.
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 Go to the management console for your virtual appliance by using its fully qualied domain name,
hps://va-hostname.domain.name:5480.
2 Log in with the user name root and the password you entered when the appliance was deployed.
Chapter 9 Troubleshooting the vRealize Automation 7.0 or 7.0.1 Upgrade
VMware, Inc. 47