This issue is resolved in vRealize Automation versions 7.4 and later.
Workaround:
To work around this issue in vRealize Automation 7.3.x, update the attached RPM file for psql manager to the nodes:
- Log in to VAMI on either VA node.
- Navigate to vRA Settings > Database tab.
- Click Async mode button. Wait for it to complete.
Note: If the button reads Sync mode - do not do anything!! We need DB cluster to be in Async mode (e.g. manual-failover mode).
- Open SSH connection to all VA nodes.
- Stop the psql-manager service on each node by running the command:
$ service psql-manager stop
- Download the attached updated RPM file for psql manager to the nodes and execute the command:
vRealize Automation 7.3.x:
$ rpm -U psql-manager-1.0.0.0-8686561.noarch.rpm
Note: if update fails, remove the current version and re-install the new one with rpm:
$ rpm -ev <old_package_name>
$ rpm -ivv <new_rpm_package_file>
$ service psql-manager start
- After the package upgrade, the psql-manager service might need to be started by running the command (all nodes):
service psql-manager restart
- Enable automatic failover again:
- Log in to VAMI page on either VA node.
- Navigate to vRA Settings > Database tab.
- Choose Sync mode.
Alternatively, to workaround the issue, disable automatic failover on the vRA cluster.
To disable automatic failover on the vRA cluster:
- Log in to VAMI page on either VA node.
- Navigate to vRA Settings > Database tab.
- Switch database to Async mode.