Component Update Shows "Patch Failed" in Fleet Management despite success

Products

• VCF Operations

Issue/Introduction

A component update initiated from Lifecycle within Fleet Manager successfully completed on the component itself.

However, the Fleet Manager's Lifecycle status for the component shows "Patch Failed" instead of "In Compliance" even after an inventory sync confirms the Current and Target versions match.

The Current Version Match the Target Version.



The logs confirm 120 minutes timeout issue:

2026-01-23T16:09:13.854Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPDay2Util] -- Running command: /usr/local/bin/vmsp pkg push <INTERNAL_REGISTRY>:<PORT> https://<REDACTED_FQDN>/repo/productPatchRepo/patches/vidb/9.0.2.0/vmsp.tar --deploy -n vmsp-platform --wait --timeout=120m --remote --kubeconfig <KUBECONFIG_SECRET> --reuse-values 2026-01-23T16:09:13.855Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPDay2Util] -- Process started

... (truncated)

2026-01-23T18:09:35.612Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPDay2Util] -- Command: /usr/local/bin/vmsp pkg push <INTERNAL_REGISTRY>:<PORT> https://<REDACTED_FQDN>/repo/productPatchRepo/patches/vidb/9.0.2.0/vmsp.tar --deploy -n vmsp-platform --wait --timeout=120m --remote --kubeconfig <KUBECONFIG_SECRET> --reuse-values exit code: 1 2026-01-23T18:09:35.612Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPDay2Util] -- Command: /usr/local/bin/vmsp pkg push <INTERNAL_REGISTRY>:<PORT> https://<REDACTED_FQDN>/repo/productPatchRepo/patches/vidb/9.0.2.0/vmsp.tar --deploy -n vmsp-platform --wait --timeout=120m --remote --kubeconfig <KUBECONFIG_SECRET> --reuse-values Output: 2026-01-23T18:09:35.612Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPDay2Util] -- Command: /usr/local/bin/vmsp pkg push <INTERNAL_REGISTRY>:<PORT> https://<REDACTED_FQDN>/repo/productPatchRepo/patches/vidb/9.0.2.0/vmsp.tar --deploy -n vmsp-platform --wait --timeout=120m --remote --kubeconfig <KUBECONFIG_SECRET> --reuse-values Error: 2026/01/23 16:09:16 bundle.vmsp.vmware.com/v1alpha1, Kind=Bundle/vmsp-platform/vmsp: created 2026/01/23 17:05:18 retrying after error: failed to watch 2026/01/23 17:42:00 retrying after error: failed to watch 2026/01/23 18:09:22 retrying after error: deployment timed out: context deadline exceeded 2026/01/23 18:09:25 retrying after error: no revisions found; 3 attempts left 2026/01/23 18:09:29 retrying after error: no revisions found; 2 attempts left 2026/01/23 18:09:35 retrying after error: no revisions found; 1 attempts left 2026/01/23 18:09:35 WARN: failed to update revision status: no revisions found Error: context deadline exceeded 2026/01/23 18:09:35 error: context deadline exceeded 2026-01-23T18:09:35.615Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPUtil] -- Writing kubeconfig <KUBECONFIG_SECRET> : <UUID_REDACTED> process exited with code: 0 2026-01-23T18:09:35.615Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPUtil] -- Fetching errors 2026-01-23T18:09:51.425Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPUtil] -- Capture errors exited with code :: 0 2026-01-23T18:09:51.426Z INFO vrlcm[189734] [pool-3-thread-42] [c.v.v.l.v.p.u.VMSPUtil] -- vmsp service pod error fetch response :: -- BUNDLE [vmsp-platform/vmsp] STATUS: Failed -- failed to download: unexpected EOF

Environment

VCF Operations 9.0

Cause

The failure status is a result of a 120-minute hardcoded timeout in Fleet Manager.

If the update process exceeds this duration, Fleet Manager incorrectly reports a failure.

Resolution

Contact Global Support Services (GSS) to open a case for assistance.