7.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for Website Component During IaaS Upgrade
- 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
- Unable to Upgrade Management Agent
- IaaS Windows Services Fail to Stop
- PostgreSQL External Database Merge Is Unsuccessful
- Delete Orphaned Nodes on vRealize Automation 7.0
- Delete Orphaned Nodes on vRealize Automation 7.0.1
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Manual PostgreSQL Database Merge
- Management Agent Upgrade is Unsuccessful
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
Bad PostgreSQL Service State Stops Upgrade and Displays Error
Message
The postupgrade scripts cause an intermient problem when vpostgres service returns incorrect status.
Problem
When the vpostgres service reports being in a bad state, upgrade fails at the /etc/bootstrap/postupdate.d/10-
postgres postupgrade script. When your upgrade fails on /etc/bootstrap/preupdate.d/10-postgres script
execution, run these three scripts, one at a time, in the following order, and restart upgrade.
(1)
rm -rf /storage/db/psql-upgrade
(2)
cat > /etc/bootstrap/preupdate.d/00-00-00-fix-psql-restart << "EOF"
#!/bin/sh
cat >> /usr/lib/vmware-bootstrap-vrva-base/psql.inc << "EOF"
function psql_restart () {
echo 'Restarting PostgreSQL server..'
service ${psql_service} stop > /dev/null
service ${psql_service} start
echo 'restart_psql finished'
}
EOF
(3)
chmod 700 /etc/bootstrap/preupdate.d/00-00-00-fix-psql-restart
Backup Copies of .xml Files Cause the System to Time Out
vRealize Automation registers any le with an .xml extension in
the \VMware\vCAC\Server\ExternalWorkows\xmldb\ directory. If this directory contains backup les
with an .xml extension, the system runs duplicate workows that cause the system to time out.
Solution
Workaround: When you back up les in this directory, move the backups to another directory, or change the
extension of the backup le name to something other than .xml.
Chapter 8 Troubleshooting the Upgrade
VMware, Inc. 45