HCX migration switchover/cut over time modified via HCX API fails and stays in "waiting for migration window" state
search cancel

HCX migration switchover/cut over time modified via HCX API fails and stays in "waiting for migration window" state

book

Article ID: 402097

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • Attempting to change/modify switchover time to start HCX migration switchover workflow via API fails for some VMs. 
    API call:  https://<HCX-MGR-FQDN-IP>/hybridity/api/mobility/migrations
"status": 200,
"method": "PUT",

     

  • Mobility group "status" switches to "Transfer Errors (1)"



Environment

VMware HCX

Cause

  • In HCX 4.10.x there is no validation step to check state being passed from user is "valid" before consuming API payload. 
  • In the API call used to modify the switchover window the "state" field was specified with a value which differs from current value stored in HCX DB for this particular migration. 
  • Passing the "state" field in the migration API payload should be left out. Instead, it is advised to check the migration state before triggering a reschedule.

Resolution

  • Upgrade to HCX 4.11 adds this validation and will provide protection against incorrect API payloads being sent / consumed by HCX-MGR. 
  • Leave out migrate "state" value in payload when modifying migration switchover window.
Powered by Wolken Software