VCF Installer fails during Cloud Proxy deployment with error "Duplicate key ONE_WAY_REMOTE_COLLECTOR:localhost"
search cancel

VCF Installer fails during Cloud Proxy deployment with error "Duplicate key ONE_WAY_REMOTE_COLLECTOR:localhost"

book

Article ID: 445231

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • Greenfield or brownfield deployment of a workload domain in VMware Cloud Foundation (VCF) 9.x fails during Cloud Proxy installation.
  • The VCF Installer task hangs or errors out during the "Wait for scale out to complete" or "Update component in VCF Operations" subtasks.
  • Error Code: LCMVROPSSYSTEM29002 may be displayed in the UI.
  • Log Analysis: The Fleet Manager system logs (WaitScaleoutSddcLcmComponentAction.java) contain the following exception: java.lang.IllegalStateException: Duplicate key ONE_WAY_REMOTE_COLLECTOR:localhost
     

Environment

VCF 9.x Installer

VCF 9.x Cloud Proxy

VCF 9.x Fleet Manager

Cause

This issue occurs due to missing DNS Reverse Lookup (PTR) records for the Cloud Proxy IP addresses.
During the initial boot, a Cloud Proxy appliance attempts to resolve its own IP address to determine its hostname. If no PTR record is found, the appliance defaults its hostname to localhost. When the VCF Installer attempts to register a second Cloud Proxy that also uses the default localhost identity, the Fleet Management orchestration layer encounters a "Duplicate Key" conflict, as it requires unique FQDNs to manage node mapping and credentials.

Resolution

To resolve the conflict and allow the installer to proceed, perform the following steps:

  1. Configure DNS: Create valid Pointer (PTR) records in your DNS server for all Cloud Proxy IP addresses associated with the deployment.
  2. Verify Resolution: Log into the Cloud Proxy console and verify that nslookup <IP_Address> returns the correct FQDN.
  3. Reboot Appliances: Restart the Cloud Proxy appliances. This triggers the startup sequence to re-query DNS and correctly set the system hostname based on the new PTR records.
  4. Restart VCF Operations Cluster:
    • Log into the Aria Operations (VCF Operations) UI.
    • Navigate to Administration > Cluster Management.
    • Take the cluster offline and bring it back online to clear the internal Suite API cache and refresh node metadata.

     5.Retry Deployment: Resume the failed "Add Cloud Proxy" task from the VCF Installer or SDDC Manager UI.

Additional Information

Related Articles:

  • KB 430069: Error Code: LCMVROPSSYSTEM29002 - Cloud Proxy node didn’t join the Operations cluster.
  • KB 439870: Deployment failure during management domain installation: Error LCMVROPSSYSTEM29002.
Powered by Wolken Software