Error: Connection Failed - vCenter FQDN, while adding vCenter as Deployment Target in VCF Fleet Management

Products

• VCF Operations

Issue/Introduction

In VCF Operations Fleet Management, administrators may be unable to add vCenters as Deployment Targets.

The task fails during the validation stage, with Error: Connection Failed - vCenter FQDN

Logs: /var/log/vrlcm/vmware_vrlcm.log

ERROR -- IOException occurred - <vcenter-fqdn>
ERROR -- Failed to trust certificate with response code - 400 and error message - Connection failed - <vcenter-fqdn>
ERROR -- Unable to get certificate for vcenter :: <vcenter-fqdn>
com.vmware.vrealize.lcm.common.exceptions.InvalidRequestException: Connection failed - <vcenter-fqdn>

Environment

VCF Fleet Management 9.x

Cause

The issue occurs when DNS is not configured on the VCF Operations Fleet Management appliance.

Resolution

Steps to configure DNS on the VCF Operations Fleet Management Appliance

1. Log in to the VCF Operations Fleet Management node using an SSH client:

   ssh root@<vcf_fleetManagement_fqdn>
   

2. Open the systemd resolver configuration file:

   vi /etc/systemd/resolved.conf
   

3. Update the DNS and domain search entries as below.

   Example:

   [Resolve]
   DNS=DNS1 server IP
   Domains=example.local corp.local
   
   Note: Use space-separated values for multiple DNS servers and search domains.

4. Save the file and exit the editor.

5. Restart the resolver service to apply the changes:

   systemctl restart systemd-resolved
   

6. Verify name resolution:

   nslookup <vcenter-fqdn>
   ping <vcenter-fqdn>
   

     7. After DNS resolution works correctly, retry adding the vCenter as a Deployment Target in VCF Fleet Management.

Example Successful Logs: /var/log/vrlcm/vmware_vrlcm.log

INFO -- Fetching certificate from <vcenter-fqdn>
INFO -- Successfully connected to https://<vcenter-fqdn>
INFO -- Certificate retrieved successfully

For additional Detail's Refer Reconfigure DNS and Domain Search on the VCF Operations Fleet Management Appliance

Additional Information

This condition typically occurs when DNS configuration was skipped or incorrectly entered during the initial deployment of the Fleet Management appliance.

Ensuring proper DNS configuration is mandatory for:

• vCenter integration

• Certificate validation

• External component communication