HCX 9.1 OSAM Force Cleanup on Completed migration deletes Migrated VM

Products

• VMware HCX

Issue/Introduction

In VMware HCX 9.1, a data loss event may occur where a successfully migrated virtual machine (VM) is unexpectedly deleted from the destination vCenter Server. This issue is exclusively limited to OS Assisted Migration (OSAM) workflows and occurs ONLY if an administrator manually performs a "Force Cleanup" operation on a completed migration.

Specific Scenario:

1. Virtual machines within a Mobility Group migrate successfully via OSAM and display a "Complete" status in the HCX UI.
2. The parent Mobility Group fails to complete and remains stuck in an "In Progress" state.
3. Canceling this completed OSAM migration and executing a Force Cleanup, results in deletion of the migrated VM.
   Note: Do not perform these actions. Canceling a completed migration and executing a Force Cleanup directly results in target VM deletion.

Environment

VCF Operations HCX 9.1

Resolution

This is a known issue impacting VMware HCX. 

Workaround:

• Do NOT execute a "Force Cleanup" or "Cancel" operation on any OSAM migration task that has reached a "Complete" status or it was migrated successfully. 
• If an OSAM Mobility Group is stuck in the "In Progress" state following a successful migration, do not attempt to clear it via the HCX user interface.
• Open a support case with Broadcom Support and refer to this KB article. For more information, see Creating and managing Broadcom support cases.

Additional Information

Subscribe to this KB article to be updated if a fix version becomes available.