Supervisor Cluster Stuck in “Configuring” State Due to Stale ESXi Task Error: ServerFaultCode – The object 'vim.Task:<task-id>' has already been deleted or has not been completely created

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

This article addresses an issue where the Supervisor Cluster in a vSphere with Tanzu environment becomes stuck in the Configuring state. This behavior is often accompanied by a general system error related to a task that no longer exists or has not been completely created on the ESXi host.

The article explains the cause and provides the recommended resolution to restore the Supervisor Cluster to a healthy state.

You may observe one or more of the following symptoms:

• The Supervisor Cluster is stuck in the Configuring state within the vSphere Client.
• The following error message appears in the vSphere UI or vCenter Server events:

      Kubernetes Worker Node is schedulable: A general system error occurred. Error message: waiting for node <node-name> to move to ready state.

      Kubernetes Worker Node commit work done in vSphere: A general system error occurred. Error message: ServerFaultCode: The object 'vim.Task:<task-id>' has already been deleted or has not been completely created.

• The related ESXi task cannot be found using vim-cmd vimsvc/task_info <task-id> and returns a ManagedObjectNotFound
• kubectl get nodes -A confirms that all worker nodes are in a Ready state, despite the Supervisor Cluster showing otherwise.

Environment

VMware vSphere Kubernetes Service
VMware vSphere with Tanzu

Cause

This issue occurs when a stale task reference remains within the ESXi host’s management layer (hostd).
The stale task causes vCenter Server to incorrectly believe that a Kubernetes worker node is still transitioning to a Ready state, even though the node is already healthy.

This condition is typically triggered by interrupted or incomplete task cleanup in ESXi.

Resolution

To resolve the issue, restart the hostd management service on the affected ESXi host to clear stale task entries.

Steps:

1. Connect to the affected ESXi host via SSH.
2. Run the following command to restart the hostd service:
   /etc/init.d/hostd restart

   
3. Wait for the service to restart successfully.
4. Verify that the stale task is cleared:
   vim-cmd vimsvc/task_list
   
   
5. Ensure that the previously reported task ID (e.g., task-#####) no longer appears.
6. Recheck the Supervisor Cluster status in vCenter Server.
   It should now transition from Configuring to Running.