VM switchover fails in HCX environment that is patched for purging policy issue

Products

• VMware HCX

Issue/Introduction

• VM switchover/cutover fails in environment that is already patched for purging policy issue KB: 429721
• The failed VMs may be less than 30 days after the base sync completion.
• The tracker script (Check_mig_tracker_issues.sql ) for purging policy shows the failed migration job in the target manager.

Environment

VMware HCX 9.x

Cause

The existing tracker script attached in the KB 429721 currently does not take into account the initiator of the migration. So if you run the tracker in target HCX manager, it may result the failed migration jobs but actually this is not actually caused by the purging policy issue.

Resolution

These failed migrations are not caused by purging policy.

An updated script attached here to identify all migrations that have the tracker issue which have been initiated from the current manager.

Check_mig_tracker_issues.sql script execution steps:

1. SSH into the HCX Manager appliance using root user.
2. Transfer the ‘tracker_ssues_updated.sql’ script to the HCX Manager.
3. Make the script executable
   

   chmod +x <Path_to_file>/tracker_ssues_updated.sql

4. Run the script
   Command:
   

   psql hybridity -f <Path_to_file>/tracker_ssues_updated.sql

5. Verify the output
   A successful run produces output similar to:
   

   migration_group_id          |             migration_id             |            tracker_job_id            |     tracker_state     | tracker_concluded |  tracker_creation_date  |   tracker_last_updated   |            parent_job_id             | parent_job_type | parent_workflow_type | parent_state | parent_previous_state | parent_concluded | parent_last_updated |            flag             | parent_missing 
   --------------------------------------+--------------------------------------+--------------------------------------+-----------------------+-------------
   ------+-------------------------+--------------------------+--------------------------------------+-----------------+----------------------+--------------
   +-----------------------+------------------+---------------------+-----------------------------+----------------
    ####-####-####-#### |  ####-####-####-#### |  ####-####-####-#### | WAIT_FOR_MAINT_WINDOW | f           
         | 2025-08-14 14:53:27.925 | 2025-12-16T10:26:21.034Z |  ####-####-####-#### |                 |                      |              
   |                       |                  |                     | PARENT_MISSING_IN_JOB_TABLE | t
     ####-####-####-#### |  ####-####-####-#### |  ####-####-####-#### | WAIT_FOR_MAINT_WINDOW | f           
         | 2025-11-03 17:09:14.052 | 2025-12-16T10:26:27.394Z |  ####-####-####-####X |                 |                      |              
   |                       |                  |                     | PARENT_MISSING_IN_JOB_TABLE | t

6. If the output of above table has entries stating "PARENT_MISSING_IN_JOB_TABLE" then you need to apply the patch if patch not applied (Refer KB:429721 ) and for the impacted migrations, reinitiate it after force cleanup Refer: Force Cleanup for a Failed or Canceled Migration

Additional Information

Synced VMs waiting for more than 30 days are not getting cutover and stuck at 'waiting for maintenance window'