VCF Operations Join Fails When Triggered from VCF Installer if VCF Operations is Configured with IP Address Instead of FQDN

Products

• VMware Cloud Foundation

Issue/Introduction

Joining an existing VCF Operations instance fails if it is configured with an IP address instead of an FQDN. This typically happens when VCF Operations uses an IP address due to an FQDN resolution failure during the bring-up process. As a result, attempting to join the existing VCF Operations instance fails with the following error:
Environment details retrieval for the given hostname failed <hostname>

Environment

VCF Installer/ SDDC Manager 9.0

Resolution

To resolve this issue, update the VCF Operations Fleet Management (VCF Ops FM) inventory with the correct VCF Operations hostname.

 

1. SSH into VCF Operations Fleet Management as root:
2. Navigate to the directory:
   cd /opt/vmware/vpostgres/current/bin  
   
   
3. Switch to the postgres user:
   su postgres 
   
   
4. Access the PostgreSQL database:
   ./psql -d vrlcm 
   
   
5. Retrieve the `node_vmid` for master node. Run the following SQL query to get master node along with their associated `node_vmid`, `value`, and `key`: 
   
   select node_vmid from vm_lcops_node_properties where value='<master-node-ip>' and key='ip'; 
   
   This query will return a list similar to the following:  
   
      node_vmid                                | value              | key  
   -----------------------------------------|--------------------|-------  
  {Unique ID}                               | {IP_Address}       | ip  
   
   
6. Update the node entry. Replace `<node_vmid>` with the `node_vmid` of the master node that you got in step 5 and set the `value` to the correct FQDN. 
   
   insert into vm_lcops_node_properties(node_vmid, value, key) values('{Unique ID},'{Correct_FQDN}','hostName');  

This will update the VCF Ops Fleet Management inventory with the correct hostname, allowing the VCF installer to retrieve the correct environment details.
Once update is done correctly , retry the failed workflow