'Cannot validate target appliance configuration as not enough information' 'config.credentials. CredentialsRequired' while upgrading to VCSA 6.5/6.7

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• The source vCenter Server Appliance hostname contains upper case letters.
• Mixed case hostname fails when upgrading to vCenter Server Appliance 6.5/6.7
• The pre-upgrade check fails with the error:

Cannot validate target appliance configuration as not enough information from the source appliance can be collected. For more details check out the server log

• In the requirements-upgrade-runner.log you see entries similar to:

2019-01-25T15:46:17.414Z ERROR upgrade.workflow_builder Internal error occurs during CollectRequirements com.vmware.vcdb
Traceback (most recent call last):
  File "/tmp/vmware-upgrade-temp-dirkTUqrI5Sql/tmp8uUQSvmUeN/py/upgrade/workflow_builder.py", line 68, in execute
    result = self.state.execute(ctx)
  File "/tmp/vmware-upgrade-temp-dirkTUqrI5Sql/tmp8uUQSvmUeN/py/upgrade/states/component_states.py", line 460, in execute
    context = self._buildContext()
  File "/tmp/vmware-upgrade-temp-dirkTUqrI5Sql/tmp8uUQSvmUeN/py/upgrade/states/component_states.py", line 381, in _buildContext
    username, password, _managedBy = getCredentialsFor(hostname)
  File "/tmp/vmware-upgrade-temp-dirkTUqrI5Sql/tmp8uUQSvmUeN/py/config/credentials.py", line 150, in getCredentialsFor
    record = _getCredentialRecordForAddress(address)
  File "/tmp/vmware-upgrade-temp-dirkTUqrI5Sql/tmp8uUQSvmUeN/py/config/credentials.py", line 141, in _getCredentialRecordForAddress
    raise CredentialsRequired('Credentials required', address)
config.credentials.CredentialsRequired: ('Credentials required', '<fqdn_in_lower_case.com>')

Note: This failure can be for any component, in this example it is com.vmware.vcdb

• Running the command /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost returns the pnid with any upper case characters in the hostname.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.5.x

Resolution

This issue is resolved in VMware vCenter Server 6.5 Update 3, available at VMware Downloads and VMware vCenter Server 6.7 Update 3, available at VMware Downloads.

Workaround:
To workaround this issue if you do not want to upgrade, enter the source vCenter Server Appliance name in lower case during the upgrade process.