Deployment of VCFA from Fleetmgmt fails with error 'deployment timed out: context deadline exceeded' Error Code : 'LCMVMSP10002'
search cancel

Deployment of VCFA from Fleetmgmt fails with error 'deployment timed out: context deadline exceeded' Error Code : 'LCMVMSP10002'

book

Article ID: 410338

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

New Deployment of VCFA from Fleetmgmt fails with error 'deployment timed out: context deadline exceeded' Error Code : 'LCMVMSP10002'

The failure is caused due to VMSP related errors 
 
vrlcm.log snippet
 
2025-09-09T13:38:58.235Z ERROR vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.t.VmspPkgPushTask] – VMSP based product deployment failed
2025-09-09T13:38:58.236Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Writing kubeconfig YXYXYXYX : <deployment_ID> process exited with code: 0
2025-09-09T13:38:58.252Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Fetching errors
2025-09-09T13:38:58.483Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Capture errors exited with code :: 0
2025-09-09T13:38:58.484Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – vmsp service pod error fetch response :: No failed pods found.
 
2025-09-09T13:38:58.484Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Fetching errors
2025-09-09T13:38:58.529Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Capture errors exited with code :: 0
2025-09-09T13:38:58.529Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – product service pod error fetch response :: No failed pods found.
 
2025-09-09T13:38:58.529Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.u.VMSPUtil] – Fetch service pod response :: No failed pods found.
No failed pods found.
2025-09-09T13:38:58.529Z ERROR vrlcm[1231] [pool-3-thread-88] [c.v.v.l.v.p.t.VmspPkgPushTask] – No failed pods found.
No failed pods found.
2025-09-09T13:38:58.529Z INFO vrlcm[1231] [pool-3-thread-88] [c.v.v.l.p.a.s.Task] – Injecting task failure event. Error Code : 'LCMVMSP10002', Retry : 'true', Causing Properties : '
{ CAUSE :: }
com.vmware.vrealize.lcm.vmsp.common.exception.DeploymentFailedException: No failed pods found.
No failed pods found.
 
 
 Based on the Error Code : 'LCMVMSP10002' validated this article#406528 and the FQDN used is all lowercase.
 
/services-logs/vmsp-platform/vcfa-2wspb/vmsp-operator-66fc79dc66-xbqd2/vmsp-operator/console-log-1757432041.log
 
2025-09-09T15:19:58.297734498Z stderr F {"level":"info","ts":"2025-09-09T15:19:58Z","logger":"bundle_controller","msg":"pulling packages","bundle":{"name":"vra","namespace":"prelude"}}
2025-09-09T15:19:58.298943017Z stderr F 2025/09/09 15:19:58 [DEBUG] GET https://<fleetmgmt_FQDN>/repo/productBinariesRepo/vra/9.0.0.0/install/vra.tar
2025-09-09T15:19:58.311359882Z stderr F 2025/09/09 15:19:58 [ERR] GET https://<fleetmgmt_FQDN>/repo/productBinariesRepo/vra/9.0.0.0/install/vra.tar request failed: Get "https://<fleetmgmt_FQDN>/repo/productBinariesRepo/vra/9.0.0.0/install/vra.tar": tls: failed to verify certificate: x509: certificate is valid for <<Fleetmgmt_shortname>>, not <fleetmgmt_FQDN>
 
2025-09-09T15:19:58.314479642Z stderr F {"level":"error","ts":"2025-09-09T15:19:58Z","logger":"bundle_controller","msg":"failed to process packages","bundle":
 
{"name":"vra","namespace":"prelude"}
,"error":"failed to download: GET https://<fleetmgmt_FQDN>/repo/productBinariesRepo/vra/9.0.0.0/install/vra.tar giving up after 1 attempt(s): Get \"https://<fleetmgmt_FQDN>/repo/productBinariesRepo/vra/9.0.0.0/install/vra.tar\": tls: failed to verify certificate: x509: certificate is valid for <<Fleetmgmt_shortname>>, not <fleetmgmt_FQDN>","stacktrace":<broadcom-internal-repository>/core-build/vmsp/vmsp/apps/source/vmsp-operator/internal/controller/bundle.(*BundleReconciler).Reconcile\n\<broadcom-internal-repository>/core-build/vmsp/vmsp/apps/source/vmsp-operator/internal/controller/bundle/bundle_controller.go:108\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Reconcile\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:116\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:303\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:263\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:224"}

Environment

VCF Operations 9.0
VCF Automation 9.0

Cause

The certificate was issued for <<Fleetmgmt_shortname>> instead of the fully qualified domain name (FQDN) <fleetmgmt_FQDN>.
For example, it was valid for <<fleetmgmt>>, not <fleetmgmt.rainpole.com>.

Resolution

  • Un-registered the VCF Operations for Logs, VCF Operations for Network from Fleet Management and un-registered Fleet Management from VCF Operations Admin Page
  • Rework on the DNS entries to bring everything in lowercase and make sure to use complete FQDN and NSlookup resolves both the short name and FQDN
  • Redeployed Fleet Management, register it again
  • Imported VCF Operations, VCF Operations for Logs &  VCF Operations for Network
  • Reconfigure Depot to download the binaries for VCFA
  • Create a new Cert
  • Redeploy VCFA using the correct cert with DNS reflecting correctly in lowercase

Additional Information

Powered by Wolken Software