Cosmetic Task Failure (404 Not Found) After Retrying a Delayed Upgrade in VCF Operations

Products

• VCF Operations

Issue/Introduction

After successfully applying a workaround and retrying an upgrade task (such as the Log Management vmsp_upgrade) that has been sitting in a failed state for an extended period, the retry task fails in the SDDC Manager UI with the following error:

An unexpected error occurred in step vmsp_upgrade. Reference Code: ########. Please contact support with this reference code. Detail: Unexpected error occurred while checking VMSP task: 404 Not Found: "{"messages": [{"level":"ERROR","id":"com.vmware.vcfms.api.NotFound","default":"Not Found"}]} <EOL>"

Environment

VCF Operations 9.1.0

Cause

This is a cosmetic failure caused by a known platform race condition 

The backend upgrade actually completes successfully. However, because the original task has existed for an extended time (e.g., ~20 days) while waiting for a retry, it has already exceeded the system's Time-To-Live (TTL) retention threshold.

Milliseconds after the backend successfully completes the retry and tags the task as "Succeeded," the system's cleanup controller immediately deletes the old task record. When SDDC Manager subsequently polls the API to confirm the final status, it receives a 404 Not Found because the record no longer exists. SDDC Manager misinterprets this missing record as a task failure and displays the error in the UI.

Resolution

No further remediation action is required. The component upgrade was successful and the component is healthy.

The "Failed" status shown in the Fleet UI is purely a cosmetic artifact of the deleted tracking record and will not block future operations or upgrades for the component.

To verify the upgrade was successful:

1. Navigate to the VCF Operations menu.

2. Go to the Components page.

3. Locate the Log Management component.

4. Verify that the status shows as Running and the version matches your target build (e.g., 9.1.0.0400.25544947).

As long as the Components page reflects the correct target version and a "Running" state, you may safely disregard the failed task in the UI and close out your maintenance window.