HCX Migration Planning waves are greyed out and cannot be deleted after being committed

Products

• VMware HCX

Issue/Introduction

In VMware HCX, users utilizing the Migration Planning feature may find that they are unable to delete specific Migration Waves. The "Delete Migration Wave" option appears greyed out within the management interface.

Symptoms:

• The Delete Migration Wave action is unavailable (greyed out) in the HCX Manager UI.
• The Migration Wave has already been "Committed" to the HCX inventory.
• Users are unable to re-import the same Migration Wave after the initial import.
• Restarting HCX services does not restore the ability to delete the committed wave.

Environment

• Product: VMware HCX
  • Version: 4.11.x (specifically observed in 4.11.4)
    • Feature: Migration Planning / Migration Waves

Cause

This is expected product behavior. By design, once a Migration Wave is "Committed," it creates a persistent record within the HCX management plane to ensure data integrity for the associated mobility groups.

Per the technical documentation, the delete operation is only permitted when a Migration Wave has not yet been committed. Once committed, the wave persists in the UI for historical tracking purposes and is not automatically removed by the standard 30-day history cleanup.

Resolution

While "Committed" waves cannot be deleted from the UI, they can be deactivated and marked as complete by following these steps:

1. Deactivate the Wave:
   • Navigate to the Migration Planning section in the HCX UI.
   • Locate the specific Migration Wave.
   • Identify all Mobility Groups associated with that wave.
   • Archive, Cancel, or Delete all associated Mobility Groups.
2. Verify Status Change:
   • Once all associated mobility groups are removed or archived, the Migration Wave will be marked as Complete automatically.
   • Note that while the wave is no longer functional, the entry will persist in the UI for historical reference.

There is currently no supported manual workaround to remove a committed wave from the database/UI without potentially compromising the integrity of the migration history.

To improve the visibility and management of the Migration Planning window, users are encouraged to archive old mobility groups to ensure waves are moved to a "Complete" status.

Additional Information

• Feature Requests: If your organization requires the ability to purge committed records from the UI, please submit a feature request by referencing the following KB: Submit a VMware by Broadcom feature request
• Documentation Reference: Migrating Mobility Groups from Migration Waves