VCF Automation deployment Failed during “Stage VCF services runtime” An unexpected error occurred in step stage_vsp_component_task_ref. Reference Code: 374BBAFA.

Products

• VCF Automation

Issue/Introduction

VCF Automation from VCF Management. The deployment is currently stuck/in progress, but the subtask "Stage VCF services runtime" failed with:

An unexpected error occurred in step stage_vsp_component_task_ref.
Reference Code: 374BFAFA.
Detail: Status polling timed out. Review the logs to check operation progress.
Increase the timeout value if the operation requires more time.

Task Info:

2026-06-01 08:55:58 UTC
Domain Manager reported:
PUBLIC_LCM_COMPONENTS_CONFIGURE_FAILED
Could not complete Fleet LCM task with ID 019e811b-f39d-761d-b4b9-d19e1f104305
Retriable operation failed to complete after 360 retries.

2026-06-01 09:16:12 UTC
Domain Manager later received HTTP 503 while polling the Fleet LCM task:
upstream connect error or disconnect/reset before headers
reset reason: connection termination

In the logs vcf-fleet-build-service-fleetbuild-XXXX/fleetbuild/console-log-1780305156.log you can find error similar to 

2026-06-01T08:58:28.435621513Z stdout F 2026-06-01T08:58:28.434Z INFO  Fleet Build 44 [lcm@4413 scPath="ops" thread="system-task-worker-12" logger="c.n.c.c.execution.WorkflowExecutor" method="terminateWorkflow:L"] [] - Workflow 019e811b-f39d-761d-b4b9-d19e1f104305 is terminated because of Workflow timed out after 21755 seconds. Timeout configured as 21600 seconds. Timeout policy configured to TIME_OUT_WF
2026-06-01T08:59:08.688894428Z stdout F 2026-06-01T08:59:08.687Z INFO  Fleet Build 44 [lcm@4413 scPath="ops" thread="https-jsse-nio-9133-exec-10" logger="c.n.c.c.execution.WorkflowExecutor" method="retry:L"] [] - Workflow INSTALL_COMPONENTS_WORKFLOW.1/019e811b-f39d-761d-b4b9-d19e1f104305 that failed due to 'Workflow timed out after 21755 seconds. Timeout configured as 21600 seconds. Timeout policy configured to TIME_OUT_WF' was retried

 

Environment

VCF 9 Automation

Resolution

The issue looks to be caused by the Infrastructure slowness (Underlying vSphere Performance issue).

Etcd latencies are also very high in the range of 500ms to 1000ms. It could be due to the slow disk performance.

Please raise the ticket with the vSphere Team to validate the affected cluster storage performance issues.