Migration Coordinator fails to migrate the ESXi TN. Cannot continue migrate because realization for transport node UUID is not SUCCESS

Products

• VMware NSX

Issue/Introduction

Symptoms:
ESXi host V2T migration failed with 2 symptoms:

1.  TN realization error
2. Log indicates 'Unable to set Ipfix DVSwitch property' error. 

Log snippet: 

2021-08-15 00:50:42,729 2500 CM.plugins.tn_base_plugin ERROR Transport node ########-####-####-####-########5432 realization failed: {'transport_node_id': '########-####-####-####-########5432', 'host_switch_states': [{'host_switch_id': '50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0', 'host_switch_name': 'Switch-vLAN', 'endpoints': [], 'transport_zone_ids': ['########-####-####-####-########d6aa', '########-####-####-####-########c325'], 'host_switch_type': 'VDS'}], 'maintenance_mode_state': 'DISABLED', 'node_deployment_state': {'state': 'success', 'details': []}, 'deployment_progress_state': {'progress': 100, 'current_step_title': 'Configuration complete'}, 'state': 'partial_success', 'details': [{'sub_system_id': '########-####-####-####-########5432', 'sub_system_type': 'Host', 'state': 'partial_success', 'failure_message': " Host configuration: host switch apply operation failed: [Error; Switch-vLAN|50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0|VDS|ApplyDvs(50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0) failed: {'fault1': {'faultMessage': ['Operation failed, diagnostics report: Unable to set Ipfix DVSwitch property: Status(bad0004)= Busy'], 'objectId': '50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0', 'msg': 'An error occurred during host configuration.', 'fault': 'PlatformConfigFault'}}]; LogicalSwitch full-sync: LogicalSwitch full-sync realization query skipped.", 'failure_code': 8804}, {'sub_system_id': '########-####-####-####-########5432', 'sub_system_type': 'HostConfig', 'state': 'partial_success', 'failure_message': "Host configuration failed on host ########-####-####-####-########5432. Error: host switch apply operation failed: [Error; Switch-vLAN|50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0|VDS|ApplyDvs(50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0) failed: {'fault1': {'faultMessage': ['Operation failed, diagnostics report: Unable to set Ipfix DVSwitch property: Status(bad0004)= Busy'], 'objectId': '50 29 f9 5e ## ## ## ##-## ## ## ## 26 5b a5 f0', 'msg': 'An error occurred during host configuration.', 'fault': 'PlatformConfigFault'}}]; .", 'failure_code': 8700}, {'sub_system_id': '########-####-####-####-########5432', 'sub_system_type': 'AppInit', 'state': 'success'}], 'failure_message': 'Host configuration failed. Number of retries : 3. Next retry attempt will be between 2021-Aug-15 01.07.23 AM and 2021-Aug-15 01.10.23 AM (UTC).', 'failure_code': 8804}
^M waiting...120

Environment

VMware NSX-T Data Center

Cause

As part of the entire migration workflow, the DVS is upgraded from 6.7 to 7.0. If DVS version is 6.7, IPFIX would not record the uplink/non-uplink port count, but when upgrading completes, IPFIX would decrement the uplink/non-uplink port count. As a result, a negative port count results. Before swapping the switch type in the migration, clearing IPFIX global property fails due to the non-zero uplink count.

Resolution

Currently there is no resolution.

Workaround:
Reboot the ESXi host and retry migration.

Additional Information

https://bugzilla.eng.vmware.com/show_bug.cgi?id=2818931
https://bugzilla.eng.vmware.com/show_bug.cgi?id=2813708#c19

Impact/Risks:
V2T migration may fail due to this issue.