Holodeck 9.1 Issue Deploy and Configure VCF Automation

[Laurn Werner]

Getting the following error message during the stage "Deploy and Configure VCF Automation"

The Fleet lifecycle 'VSP component installation' task with ID 019f4a83-d5a7-73ff-b87b-62a0c56f58ff failed. Internal errors: VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002], VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002], VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002] Reference Token: KQSPIB

<cds-icon _ngcontent-ng-c2526114375="" class="marge-right-xxs" shape="warning-standard" status="warning"></cds-icon> Failed to configure LCM components Reference Token: GNFGTQ

<cds-icon _ngcontent-ng-c2526114375="" class="marge-right-xxs" shape="warning-standard" status="warning"></cds-icon> The Fleet lifecycle 'VSP component installation' task with ID 019f4a83-d5a7-73ff-b87b-62a0c56f58ff failed. Internal errors: VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002], Deploying VCF Component. Status: Failed, Task timed out after 6h0m18s., Running Component Stage Prechecks. Status: Failed, Platform Health Check. Status: FAILED Platform Health Check Error [platform-package-core : 1 of 1 resources are not ok: vmsp-platform: wrong resource state: InProgress - package deployment is in progress;] [VCFMS-HEALTH-002], VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002], VCF Component Stage Initialization. Status: Failed, Internal error occurred. Please retry the operation or contact support if the issue persists., Internal error occurred. Failed to stage the VCF Component. Please retry the operation or contact support if the issue persists. [VCFMS-STAGE-COMPONENT-002], Deploying VCF Component. Status: Failed, Task timed out after 6h0m18s., Running Component Stage Prechecks. Status: Failed, VCF Component Stage Initialization. Status: Failed, Platform Health Check. Status: FAILED Platform Health Check Error [platform-package-core : 1 of 1 resources are not ok: vmsp-platform: wrong resource state: InProgress - package deployment is in progress;] [VCFMS-HEALTH-002], Deploying VCF Component. Status: Failed, Task timed out after 6h0m18s. Reference Token: VUNNB6

Any ideas?

[Allan Solomon Mejia]

It looks like the deployment isn't actually failing during the VCF Automation installation itself. The key error is the Platform Health Check:

 

VCFMS-HEALTH-002: platform-package-core - vmsp-platform: wrong resource state: InProgress (package deployment is in progress)

 

This usually indicates that the VSP (VMware Service Platform) package deployment is stuck or never transitioned from In Progress to Completed, so Fleet Lifecycle eventually times out while waiting to stage the component.

 

A few things I'd recommend checking:

 

1. Verify the status of the vmsp-platform package and confirm it's not stuck in an In Progress state.

2. Check Kubernetes cluster health:

kubectl get nodes

kubectl get pods -A

 

3. Look for any pods in CrashLoopBackOff, Pending, or ImagePullBackOff.

4. Confirm there are sufficient CPU, memory, and disk resources on the VCF Automation appliances.

5. Check the platform-package-core and Fleet Lifecycle logs for the underlying cause of the package deployment stall.

6. If this is running in a Holodeck 9.1 nested lab, also verify the underlying ESXi hosts aren't resource constrained. I've seen package staging hang in environments where storage performance or memory is limited.

 

Could you share:

• The exact VCF version/build (9.1 GA or later patch?)
• Whether this is a Holodeck nested lab or a physical deployment
• The output of kubectl get pods -A (or a support bundle if available)

 

That should help narrow down whether this is a package deployment issue, a Kubernetes health problem, or a resource constraint.