-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
2.8.0
-
None
-
Quality / Stability / Reliability
-
True
-
-
True
-
-
Description of problem:
Create VM with 2 OS (rhel9.5 /dev/sda2, rhel8.10 /dev/sdb2, both with static ip addres), start it with rhel8.10(/dev/sdb2), create warm migrate plan with "Root Device: First root device" and "Preserve static ip: on", after migration: it's running with correct os (rhel9.5 /dev/sda2), but the static ip address is not existed.
Version-Release number of selected component (if applicable):
MTV 2.8.0
How reproducible:
100%
Steps to Reproduce:
1) Prepare VM: mtv-func-t1-rhel-2os with 2 rhel OS: rhel9.5(/dev/sda2), rhel8.10(/dev/sdb2), both have statip ip setting for interface: ens192.
2) Start VM, it's running with rhel8.10 (/dev/sdb2), create warm migration plan to migrate it to ocp cluster with "Root Device: First root device" and "Preserve static IPs: on"

3) The plan executed successfully, login to VM, check the VM is running with first root device: rhel9.5(/dev/sda2), but the static ip address is not existed
Actual results:
In step3: The VM is running with correct OS, the static ip address is not existed
Expected results:
In step3: The VM is running with correct OS, and the static ip address no change
- is related to
-
RHEL-134173 RFC: virt-customize support dualboot
-
- Planning
-