VCHA fails to configure after upgrading to vCenter Server 7.0 U2

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• After using the wizard to configure VCHA, it fails with the error

The operation is not allowed in the current state

• The following errors are present in /var/log/vmware/vcha/verify-postgres-setup.log

2021-05-22T12:12:12.688Z INFO verify-postgres-setup Checking if PostgreSQL is setup correctly.
2021-05-22T12:12:12.688Z INFO verify-postgres-setup running command ['/opt/vmware/vpostgres/current/bin/pg_isready', '--host=123.123.123.4']
2021-05-22T12:13:36.376Z INFO verify-postgres-setup Done running command
2021-05-22T12:13:36.376Z INFO verify-postgres-setup rc = [2], stdout = [123.123.123.4:5432 - no response
], stderr = []
2021-05-22T12:13:36.376Z ERROR verify-postgres-setup Failed to run all the checks:
2021-05-22T12:13:36.376Z ERROR verify-postgres-setup ['Traceback (most recent call last):\n', '  File "/usr/lib/vmware-vcha/scripts/verify_postgres_setup.py", line 45, in main\n    logging.error(\'PostgreSQL is not listening on %1.\' % ipAddress)\n', 'ValueError: incomplete format\n']

• The vCenter is configured with AD integration
• VCHA was configured and working prior to upgrading to 7.0 U2

Environment

VMware vCenter Server 7.0.x

Cause

This issue is due to a problem with authentication handling in vpostgres, specifically GSSAPI requests.

Resolution

This issue is resolved in vCenter Server 7.0 U2c.

For download information see Download Broadcom products and software