-
Bug
-
Resolution: Done-Errata
-
Critical
-
2.7.11
-
Incidents & Support
-
3
-
False
-
-
True
-
-
-
Critical
-
Customer Reported
Description of problem:
Windows VM have a static route, configured as below:
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.0 255.255.255.0 10.74.239.4 90 <== static route
0.0.0.0 0.0.0.0 10.74.239.254 Default <== default g/w
With this conf, forklift inventory shows 2 gateway IP for the device:
"guestIpStacks": [ { "device": "0", "gateway": "10.74.239.254", <== Default gateway "dns": [ "fec0:0:0:ffff::1", "fec0:0:0:ffff::2", "fec0:0:0:ffff::3" ] }, { "device": "0", "gateway": "10.74.239.4", <== static route gateway "dns": [ "fec0:0:0:ffff::1", "fec0:0:0:ffff::2", "fec0:0:0:ffff::3" ] },
Following is the data from the VMware Mob, we have the destination n/w under "network", with default route marked as "0.0.0.0", but forklift is not considering this and marking both IP address as gateway IP of the interface.
gateway | NetIpRouteConfigInfoGateway | |
Name | Type | Value |
---|---|---|
device | string | "0" |
ipAddress | string | "10.74.239.254" |
network | string | "0.0.0.0" |
prefixLength | int | 0 |
Name | Type | Value |
gateway | NetIpRouteConfigInfoGateway | |
Name | Type | Value |
device | string | "0" |
ipAddress | string | "10.74.239.4" |
network | string | "192.168.1.0" |
prefixLength | int | 24 |
For retrieving the gateway IP and to pass it to v2v, the code iterates over GuestIpStacks [1], matching only on the "device" field. Since there are two gateway IPs, it ends up setting the last one in the list, ie 10.74.239.4 here as a gateway IP.
10.74.239.4 is passed to the v2v:
/usr/libexec/virt-v2v-in-place -v -x -i libvirtxml --root first --mac 00:50:56:86:8b:30:ip:10.74.234.211,10.74.239.4,21,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3 /mnt/v2v/input.xml
v2v logs:
Running the virt-v2v-inspector with args: [-v -x -if raw -i disk -O /var/tmp/v2v/inspection.xml --root first --mac 00:50:56:86:8b:30:ip:10.74.234.211,10.74.239.4,21,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3 /var/tmp/v2v/nijin-win-2019-sda]
ipconfig o/p after migration
Ethernet adapter Ethernet Instance 0: Connection-specific DNS Suffix . : IPv6 Address. . :2620:52:0:4a80:aa40:bef9:736a:89cc Link-local IPv6 Address . . .: fe80::2904:e3dc:42b1:f62f%5 IPv4 Address....... ... : 10.74.234.211 Subnet Mask . .:255.255.248.0 Default Gateway. ........ : fe80::96f7:ad00:968e:fc40%5 fe80::200:5eff: fe00:201%5 10.74.239.4 <===
Version-Release number of selected component (if applicable):
Migration Toolkit for Virtualization Operator 2.8.1
How reproducible:
Always
Steps to Reproduce:
1. Created a static route on the VM: route -p ADD 192.168.1.0 MASK 255.255.255.0 10.74.239.4 METRIC 90 2. Restart the VM, check in the forklift inventory if it's now showing both the gateway IP address. 3. Migrate this VM to OpenShift Virtualization. Ensure that "preserve static ip" option is enabled. 4. After migration, check the default gateway of the VM, it will be the static route gateway.
Actual results:
Static route gateway is passed as default gateway while doing migration
Expected results:
Correct default gateway should be configured on the VM.
Additional info:
- clones
-
MTV-2408 Static route's gateway is passed as the default gateway during migration
-
- Closed
-
- links to
-
RHBA-2025:148280 MTV 2.8.2 Images
-
RHBA-2025:148426 MTV 2.7.12 Images