HCX OSAM Migration stuck in "Canceling Migration"

Products

• VMware HCX

Issue/Introduction

• You are unable to cancel an HCX OSAM migration.
• The task to cancel the migration was done using the Legacy HCX UI.
• From the HCX Manager UI, the task shows as "Cancelling Migration":
  
• Using the "Force Cleanup" does not change the status from "Cancelling Migration".

Environment

VMware HCX 4.11

VCF Operations HCX 9.0

Resolution

This is a known issue impacting VMware HCX 4.11 and VCF Operations HCX 9.0.

Workaround:

1. Select the affected VM, and click on the Force Cleanup, for more information: Force Cleanup for a Failed or Canceled Migration
   Note: The migration will remain in the “Canceling Migration” state in the legacy HCX migration UI; however, the force cleanup is required to clean up the backend state. This will allow the migration to be triggered again from the new UI.
2. Uninstall the sentinel from the Sentinel Management Page, refer to: Uninstalling HCX Sentinel Agent Software
3. If the Sentinel Management page displays the message "migration is running for this system" due to stale migration state and the agent cannot be removed through the UI, you can perform a manual uninstallation directly from the Guest OS.
4. Install the sentinel bundle which will show up as new system: Downloading and Installing HCX Sentinel Agent Software
5. Trigger the migration using the new UI (by switching to "New Display").
   Note: After applying the workaround described, the VM status will still show as "Canceling Migration" however, it will allow this VM to be migrated again.

 

Additional Information

Note: After reinstalling the Sentinel Agent, the Guest OS VM will appear as Connected in the Sentinel Management Page. However, a stale entry for the same VM may still appear in a Disconnected state. This behaviour is expected. Please refer to [HCX] OSAM Sentinel software remains listed as installed on VMs where it was uninstalled. 

To remove the stale VM entry, delete the existing Service Mesh and recreate it. If the deletion fails with a message indicating that migrations are still in progress. You may need to use the force delete option to remove it after you have confirmed that no active migrations exist.