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
3 Select vRA > Cluster.
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.
Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient
Free Space
If sucient free space is unavailable on the root partition of the vRealize Automation appliance host,
upgrade cannot proceed.
Solution
This procedure increases the free space on the Disk 1 root partition of the vRealize Automation appliance
host. In a distributed deployment, perform this procedure to increase the free space on each replica node
sequentially, and then increase the free space on the master node.
N When you perform this procedure, you might see these warning messages:
n
WARNING: Re-reading the partition table failed with error 16:
Device or resource busy. The kernel still uses the old table. The
new table will be used at the next reboot or after you run
partprobe(8) or kpartx(8) Syncing disks.
n
Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a result, the old partition(s)
will remain in use. You should reboot now before making further changes.
Ignore the message You should reboot now before making further changes. If you reboot your system
before step 10, you corrupt the upgrade process.
Procedure
1 Power on the VMware vRealize ™ Automation appliance host virtual machine and log in as with a
secure shell connection as the root user.
2 Run the following commands to stop services.
a service vcac-server stop
b service vco-server stop
c service vpostgres stop
Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
48 VMware, Inc.