Description of problem:

We ever had a customer requirement to keep the default gateway setting even if the gateway is not in the subnet, more details in MTV-2018.

Cold migrate win2019 VM from vCenter 7 to OCP cluster, the default geteway setting is no longer exist after migration. (The ip/subnet/gateway settings are following the settings in customer case)

Version-Release number of selected component (if applicable):

MTV 2.9.0(forklift-fbc-prod-v419:on-pr-155cb285a7b3e3798731cf93956a32dd60202e11) with CNV 4.19.1

How reproducible:

100%

Steps to reproduce:

1) Create VM: mtv-func.win2019_79 on vCenter7 with gateway settings as below: The default gateway is not in the subnet

2) Create cold migration plan to migrate VM to ocp cluster with preserve static ips: on, map the source networks to nad bridge networks, check one of the interface default gateway setting is no long exist.

3) Check the v2v conversion pod log with correct gateway settings, more details in file: [^mtv-win2019-vm-2522-rxlb9-virt-v2v.log]^{forklift-controller pod log: [^forklift-controller-74c4b7dcbb-zt9dv-main.log]}

4) Check the network scripts in target VM, the command line with defaultgateway setting as below:

5) Check the log in VM for network configure.bat

Actual results:

Step2: The VM default gateway setting is no longer exist in target VM

Expected results:

Step2: The VM default gateway setting is exist in target VM