VCF "Configure Lifecycle Components" Task Fails at the "Register Software Depot" Step with a Connection Timeout to the Fleet Depot Service

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

Symptoms

During a VMware Cloud Foundation (VCF) upgrade, the "Configure Lifecycle Components" task fails with the following error in the UI:

The SDDC lifecycle task 'Configure service' (<UUID>) failed. Task with ID '<ID>' from SDDC lifecycle with ID '<ID>' has completed with failure(s). Check the errors in the next sub-task(s) for more details. Reference Token: <TOKEN>

VCF Installer logs:

ERROR ... [<TOKEN>] PUBLIC_CONFIGURE_SDDC_LCM_TASK_ERROR The SDDC lifecycle task Configure service (<UUID>) failed. Task with ID '<UUID>' from SDDC lifecycle with ID '<UUID>' has completed with failure(s). Check the errors in the next sub-task(s) for more details.

SDDC Build service logs show error:

ERROR sddc-build-service 54 [lcm@4413 scPath="ops" thread="system-task-worker-27" logger="c.b.v.l.s.b.service.DepotServiceImpl" method="registerFdsInSddcManager:134"] [<UUID> taskId=<UUID>] - Failed to register FDS as service config

followed by 

ERROR - Request failed after 30001ms: PUT https://<SDDC-MANAGER_FQDN>/v1/services-config?skipStrictValidation=false

..... stdout F java.net.SocketTimeoutException: timeout

Additionally, you may see the following non-fatal error in the installer logs, which can be ignored:

Caused by: org.springframework.web.client.HttpClientErrorException$BadRequest: 400 on POST request for "/v1/users": {"errorCode":"PERMISSION_ALREADY_EXISTS","arguments":[],"message":"One or more User(s) or Group(s) with the selected Role already exist","referenceToken":"<TOKEN>"}

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

The deployment failure is caused by a network connectivity blockage between the SDDC Manager appliance and the Fleet Deployment Service (FDS).

If the SDDC Manager cannot reach the Fleet service over port 443, the validateServiceConnectivity() method hangs indefinitely because it lacks a defined connection timeout.

Note: The PERMISSION_ALREADY_EXISTS error logged during the upgrade is transient and is automatically handled by the installer (the service account is deleted and re-created). It does not impact the success of the workflow and can be ignored.

Resolution

To resolve this issue, ensure full network connectivity is available between the SDDC Manager instance and the Fleet Deployment Service.

1. Verify Network Paths: Confirm that your network infrastructure allows traffic on TCP port 443 between your SDDC Manager instance and the Fleet service.
   
   
2. Firewall Configuration: Ensure that any physical or virtual firewalls between the two endpoints are configured to permit this communication.
   
   
3. Retry Task: Once the network path is verified and traffic is permitted, retry the failed lifecycle task from the SDDC Manager UI.