Connecting to an existing VCF Operations manager instance during VCF 9.0 deployment fails with an internal server error

Products

• VMware Cloud Foundation

Issue/Introduction

• Connecting to an existing VCF Operations manager instance during the deployment of a VCF 9.0 environment fails with internal server error.
• The /var/log/vmware/vcf/domainmanager/domainmanager.log file on the VCF installer appliance contains the following error messages:
  
  org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://<vcf-ops-fqdn>/casa/sysadmin/slice/vmware/buildinfo": Certificate for <vcf-ops-fqdn> doesn't match any of the subject alternative names: [localhost]
ERROR [vcf_dm,6a20df40fe7f593ebdfd91bfa81cf9c6,1b78] [c.v.v.v.services.DiscoveryService,http-nio-XXXX-7200-exec-2]  Unable to conduct discovery against VCF Ops address <vcf-ops-fqdn>


• Executing the hostname command directly on the VCF Operations node returns a short name instead of a fully qualified domain name (FQDN).

Environment

VMware Cloud Foundation 9.0

Cause

The VCF deployment process requires the target VCF Operations manager instance to have a FQDN assigned as its hostname. The connection verification fails because the hostname is configured as a short name, causing a mismatch with the subject alternative name (SAN) field of the SSL certificate which only contains localhost.

Resolution

1. Reconfigure the VCF Operations appliance hostname to a fully qualified domain name (FQDN) by referring to KB  How to change a node hostname in Aria Operations
2. Regenerate and apply an SSL certificate on the VCF Operations appliance that contains the correct FQDN within the subject alternative name (SAN) field by referring to KB Configure a Certificate For Use With VCF Operations
3. Retry the connection step in the VCF deployment wizard.