Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-2626

The Preserve Static IP option doesn't work when there's more than one network connection using the same IP address.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Normal Normal
    • None
    • 2.8.4
    • Guest
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • True

      Description of problem:

      After successfully migrating a virtual machine from a migration plan with the Preserve Static IP option enabled, udev rules were not created in the VM's operating system. Consequently, the network interface names were not maintained as expected.

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

      MTV 2.8.4

      How reproducible:

      Always
      

      Steps to Reproduce:

      1. on the VM: Create two NetworkManager connections (profiles) using the same IP address.
      2. Create a new plan and set Preserve Static IP option.

      Actual results:

      After the migration to OpenShift, the VM does not retain its network interface name because the udev rules were not created during the migration by the v2v network_config_util.sh script

      Expected results:

      That the udev rules would be created and that the interface name would be maintained after the migration

      Additional info:

      In my lab, I tested by running the network_config_util.sh script directly on the VM, and we can reproduce the same behavior without needing to migrate the virtual machine.I've added screenshots showing the results of running the script directly on the VM.NOTE: It was necessary to manually create the /tmp/macToIP file and place the expected content inside it, for example: 00:50:56:a2:7d:e7:ip:192.168.10.2,,24. When I removed one of the NetworkManager profiles and then ran both a new migration plan with preserve option enabled nd the script manually on the machine, the udev rule was correctly created, and as a result, the interface name was not changed.

        1. Screenshot From 2025-05-29 13-58-58.png
          63 kB
          Paulo Pacifico
        2. Screenshot From 2025-05-29 14-02-56.png
          31 kB
          Paulo Pacifico
        3. Screenshot From 2025-05-29 14-04-28.png
          39 kB
          Paulo Pacifico
        4. Screenshot From 2025-05-29 14-05-23.png
          24 kB
          Paulo Pacifico

              gcheresh@redhat.com Genadi Chereshnya
              ppacific@redhat.com Paulo Pacifico
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: