-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.9.2
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
Description of problem:
When using 'preserveStaticIPs: true' in a migration plan on a vSphere VM that has a mix of static IPs and DHCP IPs, the static IP configuration might not be migrated correctly.
Version-Release number of selected component (if applicable):
MTV 2.9.2 on OCP 4.19
How reproducible:
Always
Steps to Reproduce:
Test #1: 1st NIC with a static IP and 2nd NIC with DHCP 1. Migrate the VM from vSphere to OCPV 2. The migrated VM will not have an IP address on either interface 3. The fist NIC is renamed from ens192 to enp1s0 and has no IP address 4. The second NIC is renamed from ens224 to enp2s0 and has no IP address Test #2: 1st NIC with DHCP and 2nd NIC with a static IP 1. Migrate the VM from vSphere to OCPV 2. The migrated VM will only have an IP address on the 2nd NIC 3. The first NIC is renamed from ens192 to enp1s0 during migration 4. The second NIC keeps the name ens224 during migration and has an IP address
Expected results:
Ideally, all NIC configuration will be migrated, but at least the two test scenarios above should yield the same results (i.e. the static NIC works and the DHCP NIC does not).
Additional info:
The test VM is running RHEL 9.6 with relatively recent updates. When the VM only has 1 NIC with a static IP, or 2 NICs with static IPs, all of the NICs keep their original names and come online, as expected.
- is blocked by
-
MTV-3660 [GA] MTV ansible hook example
-
- New
-