← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1984009] [NEW] libvirt live-migration fails when network MTU is different

 

Public bug reported:

After changing the MTU of an OpenStack network, attempting to live-migrate an existing instance fails with e.g.:
ERROR nova.virt.libvirt.driver [-] [instance: f3807b12-fa7e-4da8-a688-c5507fb66891] Live Migration failure: unsupported configuration: Target network card MTU 9000 does not match source 1500: libvirt.libvirtError: unsupported configuration: Target network card MTU 9000 does not match source 1500

Indeed, the MTU should not change as per:
https://bugzilla.redhat.com/show_bug.cgi?id=1623157

However, it should be the case that libvirt live-migration code should
retain the MTU specified in the source domain. If we do that, live-
migration still works.

** Affects: nova
     Importance: Undecided
     Assignee: Tyler Stachecki (tstachecki)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Tyler Stachecki (tstachecki)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1984009

Title:
  libvirt live-migration fails when network MTU is different

Status in OpenStack Compute (nova):
  New

Bug description:
  After changing the MTU of an OpenStack network, attempting to live-migrate an existing instance fails with e.g.:
  ERROR nova.virt.libvirt.driver [-] [instance: f3807b12-fa7e-4da8-a688-c5507fb66891] Live Migration failure: unsupported configuration: Target network card MTU 9000 does not match source 1500: libvirt.libvirtError: unsupported configuration: Target network card MTU 9000 does not match source 1500

  Indeed, the MTU should not change as per:
  https://bugzilla.redhat.com/show_bug.cgi?id=1623157

  However, it should be the case that libvirt live-migration code should
  retain the MTU specified in the source domain. If we do that, live-
  migration still works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1984009/+subscriptions