Resolving Orphaned HCX Tasks for SDDC environment within vCenter
search cancel

Resolving Orphaned HCX Tasks for SDDC environment within vCenter

book

Article ID: 382453

calendar_today

Updated On:

Products

VMware Cloud on AWS VMware HCX

Issue/Introduction

In some instances, HCX tasks may become orphaned and stuck in vCenter, with no ability for customers to cancel or complete these tasks through standard processes.

Environment

  • SDDC Environment
  • VMware vCenter
  • VMware HCX

Cause

This issue typically occurs when a migration task becomes orphaned in vCenter but is no longer actively associated with any ongoing migration.

This can happen when

  • A migration fails or succeeds but the task itself doesn't properly complete
  • The state of the VM changes during the migration process
  • The task loses its association with the actual migration

Common indicators include

  • Task appears stuck at a high completion percentage
  • No corresponding active migration visible in HCX interface
  • Task cannot be cancelled through standard vCenter interfaces
  • No actual data transfer or migration activity occurring

Resolution

If you encounter a hung HCX Cold Migration task in your SDDC environment

  1. Open a support case with the HCX team at Broadcom
  2. Provide details about the hung migration task
  3. Broadcom Support will:
    • Verify no active migration is associated with the task
    • Confirm the task is truly orphaned in the system
    • Change the task status to "success" using backend management tools