Adding vCenter server as a Deployment Target in VCF Fleet Manager fails at Validate to add vCenter for appliance deployment
search cancel

Adding vCenter server as a Deployment Target in VCF Fleet Manager fails at Validate to add vCenter for appliance deployment

book

Article ID: 422240

calendar_today

Updated On:

Products

VCF Operations VMware Cloud Foundation

Issue/Introduction

  • The Fleet Manager is unable to add/validate a vCenter server as a Deployment Target. The error observed from the VCF UI:

    Validate to add vCenter for appliance deployment.
    Note: If the desired vCenter is not shown, please add it under VCF Operations > Administration > Integrations

     

  • The log ( /var/log/vrlcm/vmware_vrlcm.log) shows a connection failure to the SDDC Manager API endpoint:
     INFO vrlcm[1295] [pool-3-thread-19] [c.v.v.l.l.u.CompareSddcAndVcServiceUtil]  -- create svc acc for vc using sddc payload :: com.vmware.vrealize.lcm.lcops.common.inventory.SddcManagerServiceAccountForVC@####
     INFO vrlcm[1295] [pool-3-thread-19] [c.v.v.l.l.u.VCFRestClient]  -- input map :: java.io.ByteArrayInputStream@####
     INFO vrlcm[1295] [pool-3-thread-19] [c.v.v.l.l.u.VCFRestClient]  -- Connect URL : https://[SDDC]/v1/tokens
    ERROR vrlcm[1295] [pool-3-thread-19] [c.v.v.l.l.u.VCFRestClient]  -- Exception occurred while getting VCF access token.
    java.net.SocketTimeoutException: connect timed out
            at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
            at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:?]
            
     ERROR vrlcm[1295] [pool-3-thread-19] [c.v.v.l.l.u.CompareSddcAndVcServiceUtil]  -- Exeption occurred when getting auth token.
    com.vmware.vrealize.lcm.lcops.common.exception.VCFAPITokenRetrivalException: Exception occurred while getting VCF access token.
    
    
     INFO vrlcm[1295] [pool-3-thread-19] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : '##########', Retry : 'false', Causing Properties : '{ CAUSE ::  }'
    com.vmware.vrealize.lcm.common.exception.EngineException: Exception while performing vCenter validation
            at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.FetchAndValidateVCFromOpsTask.execute(FetchAndValidateVCFromOpsTask.java:129) [vmlcm-vropsplugin-core-9.0.1.0-SNAPSHOT.jar!/:?]
            at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) [vmlcm-engineservice-core-9.0.1.0-SNAPSHOT.jar!/:?]
            at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
            at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
            at java.base/java.lang.Thread.run(Unknown Source) [?:?]
    
     

 

Environment

VMware Cloud Foundation 9.0.0.0

Cause

The root cause is a network connectivity failure between the Fleet Manager appliance and the SDDC Manager appliance on the required API port.

Resolution

Verify and ensure that TCP port 443 (HTTPS) is open and accessible from the Fleet Manager appliance to the SDDC Manager appliance.

Steps to Verify and Resolve:

  1. Verify Network Connectivity:

    • Log in to the Fleet Manager appliance via SSH.

    • Execute the following command to test the raw TCP connection to SDDC Manager on port 443:

      curl -v telnet://<FQDN of SDDC Manager VM>:443
      
      • If the test fails (e.g., hangs, times out, or shows "Connection refused"), the network path is blocked.

  2. Correct Network Path:

    • If the connectivity test fails, work with the Network and Security teams to review and correct firewall rules and/or network routes to permit traffic on TCP port 443 from the Fleet Manager appliance to the SDDC Manager appliance.
      Reference Article:https://ports.broadcom.com/home

  3. Re-attempt Validation:

    • Once the network path is verified to be open on port 443, re-attempt the add/validate vCenter operation in the Fleet Manager UI.