Solved - Upgrading a vRealize Appliance to vRA 6.2 fails when using a vRealize Appliance configured as a standalone PostgreSQL database

Symptoms

• When a vRealize Appliance has been configured as a dedicated standalone PostgreSQL database server you receive an error when attempting to upgrade the appliance to vRealize 6.2
• The vRealize Automation services run on another vRealize Appliance that connects to the standalone PostgreSQL database server

Cause

This issue occurs because the upgrade runs a post-install script that requires the vRealize Appliance to be connected to a PostgreSQL database.

By default, when configuring a vRealize Appliance as a standalone PostgreSQL database you do not configure the appliance to connect to the local database. Additionally, configuring this connection on a standalone PostgreSQL database causes a configuration setting to change that prevents external connections such as those from the vRealize Appliances running the Automation services.

Resolution

Perform a backup of configuration files and snapshots of the vRealize Appliances prior to performing these steps.

1. Open a web browser and log in to the standalone PostgreSQL database server appliance https://FQDN:5480
2. Navigate to vCAC Settings -> Database
3. Enter the following:
   1. Host: 127.0.0.1
   2. Port: 5432
   3. Database: DatabaseName
   4. User: UserName
   5. Password: Password
4. Click Save Settings
5. Open a console or SSH session to the standalone PostgreSQL database server appliance
6. Run the following commands:
   1. sed -i -re 's/^(listen_addresses=.)(localhost)(.*)/\1*\3/' /var/vmware/vpostgres/current/pgdata/postgresql.conf
   2. service vpostgres restart
7. Attempt the Appliance upgrade again using the steps in the Upgrading to vRealize Automation 6.2 or later documentation