7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- 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
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- 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 Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- 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
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
Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on
a IaaS Node
Management Agent or Certicate is not upgraded on a IaaS node and error message appears in the
management console.
Problem
If the upgrade fails to upgrade on a IaaS node and error messages about the Management Agent or
Certicate appear in the management console, use these suggestions to troubleshoot the problem.
n
Check the Management Agent log on the aected node for errors.
n
Check if the Management Agent was auto-upgraded by examining the version number in Programs
and Features.
n
If the Management Agent is upgraded, ensure that its service is running.
n
If the Management Agent is upgraded and running, restart upgrade on the virtual appliance.
n
If the Management Agent is not upgraded, perform a manual upgrade of the Management Agent. Open
a browser and navigate to the VMware vRealize Automation IaaS Installation page on the vRealize
Automation appliance at hps://virtual_appliance_host:5480/installer. Download and run the
Management Agent Installer. Restart upgrade on the virtual appliance.
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..'
Upgrading from vRealize Automation 6.2 to 7.1
50 VMware, Inc.