Retrying an individual VM migration in HCX, after its initial failure has been resolved, places the migration into a queued state
search cancel

Retrying an individual VM migration in HCX, after its initial failure has been resolved, places the migration into a queued state

book

Article ID: 404886

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • After an HCX VM migration fails and you address the underlying issue, reattempting the migration via the 'retry' option causes it to become stuck in a queue.
  • Below, logging was observed in the /common/logs/admin/app.log file of the HCX Manager/Connector.
    <time stamp>  [MobilityMigrationService_SvcThread-15678, Ent: HybridityAdmin, , TxId: ########-####-####-############] INFO  c.v.h.s.m.jobs.MobilityMigrationJob- existing Migration Tracker found for migration id: ########-####-####-############ with jobId: ########-####-####-############. Hence will skip creating one.

Environment

VMware HCX

Cause

Using the Retry Migration action on an individual migration record rather than on the migration group can cause the cancellation workflow to become stuck and prevent further progress. In the given state, the Force Cleanup action will also remain ineffective.

Resolution

This issue is resolved in VMware HCX 4.11.1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.