Clear stale HCX tasks within vCenter

Products

• VMware HCX
• VMware Cloud on AWS
• VMware Cloud on Dell EMC
• VMware vSphere ESXi

Issue/Introduction

This KB article provides steps for clearing the outdated HCX task from the vCenter "Recent Tasks" list.

 

For example:

The customer may be seeing stale migration tasks within the Cloud vCenter "Recent Tasks" field, when the migration shows as completed or canceled from within the HCX UI.

Environment

VMware Cloud on AWS

VMware HCX

VMware vSphere 

Cause

The tasks have completed, but vCenter never processed the final completion of that fact. If it was completed recently enough, you will see evidence of completion in the logs. This could be due to temporary contention for vCenter or interruption in the communication to HCX at the time of completion.

Resolution

First, follow the KB for clearing hung, stuck, or stale tasks from the "Recent Tasks" Panel. 

If following that KB does not address the issue, move on to the next steps:

Cancel/Remove the stale task from within the vCenter MOB (Managed Object Browser):

• Access the Cloud vCenter MOB - https://vcenter_FQDN>/mob/?moid=TaskManager.

In MOB page of vCenter, Click on Content , search for the TaskManager, Under RecentTask Field, click on each Task Info and ensure the task corresponds to the Task that is listed in the Recent Task.

• Manually inspect the info property and note down the descriptionID, startTime of the task to ensure that you on the right task that needs to be acknowledged.
• Once the task is identified, invoke SetTaskState with parameters as below
  state : success
result and fault: Both should be empty
• Click on InvokeMethod

The above step marks the stale task as success

Workaround:

If removing the stale HCX task within the vCenter MOB is not successful, please create an SR (Creating and managing Broadcom support cases) with VMC GS with the ask to help clear the stale task from vCenter.
 
Please Note: A restart of the VPXD service may be needed and it will impact any ongoing migrations as well as access to the Cloud vCenter for about 2-3 minutes.

Additional Information

Impact/Risks:
There should be no impact to the vCenter or HCX migrations. This is just a stale task that is seen within the vCenter that can be removed by following the resolution steps and or workaround.