This article is intended to give guidance to users on how to remediate the issue.
During a past VI Domain creation invocation there was a failure that required remediation and restart of the operation. This behavior results in the vCenter associated with the successfully created domain having incorrect SSO status in the VCF platform database.
This issue is fixed in VCF 5.1.
Workaround:
Follow the steps should below:
SSH to the SDDC virtual machine.
Connect to the platform database via psql: psql -h localhost -U postgres -d platform -c "select * from vcenter;"
Review the records in the vcenter table for the value ACTIVE in the status column and value NOT_JOINED for the join_sso_status column.
Update any occurrences that match the condition in 3. using the following SQL update statement: UPDATE vcenter SET join_sso_status='JOINED' where id=<ID for a record identified in 3.>;