In Rocky, we started including the MTU for networks when vif_type
is bridge or tap and libvirt >= 3.3.0, however this also meant
that we started specifying the MTU when doing live migrations.
It seems that the guest ABI changes when setting the MTU which
means that live migrations will fail. This broke the live migration
of any instance that was launched prior to upgrading to Rocky, as
it was not loaded with the ABI having host_mtu specified.
This is a passing (negative) test-case which will include a follow
up patch that contains a fix and correcting tests.
(cherry picked from commit 29ee8011b4e1cf5371b1aa9c6c0f930eb49fe795)
Reviewed: https:/ /review. openstack. org/614040 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=d28e7346ec1 b3730d9bedf4a1b 84223b89083635
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit d28e7346ec1b373 0d9bedf4a1b8422 3b89083635
Author: Mohammed Naser <email address hidden>
Date: Mon Oct 29 19:18:26 2018 +0100
Add tests for bug #1800511
In Rocky, we started including the MTU for networks when vif_type
is bridge or tap and libvirt >= 3.3.0, however this also meant
that we started specifying the MTU when doing live migrations.
It seems that the guest ABI changes when setting the MTU which
means that live migrations will fail. This broke the live migration
of any instance that was launched prior to upgrading to Rocky, as
it was not loaded with the ABI having host_mtu specified.
This is a passing (negative) test-case which will include a follow
up patch that contains a fix and correcting tests.
(cherry picked from commit 29ee8011b4e1cf5 371b1aa9c6c0f93 0eb49fe795)
Related-Bug: #1800511 3e808cb9dda3a55 f853f048a3e
Change-Id: Ia2fe50d727b1f8