Public bug reported:
Description
===========
We got the mtu error as below on the source compute node, when live
migrating an instance which have two interface from both vxlan tenant
network and vlan provider networks.
"Target network card MTU 0 does not match source 1450:
libvirt.libvirtError: unsupported configuration: Target network card MTU
0 does not match source 1450"
Steps to reproduce
==================
1. Create an instance from vlan provider network or vxlan tenant network.
2. Attach the second interface. If instance created with vxlan tenant network
then attach vlan provider network. If instance created with vlan provider
network then attach vxlan tenant network.
3. Try to live migrate the instance.
Expected result
===============
Live migration should be succeded
Actual result
=============
We got the error below on the source compute node (nova-compute)
"Target network card MTU 0 does not match source 1450:
libvirt.libvirtError: unsupported configuration: Target network card MTU
0 does not match source 1450"
Scenarios
===============
1. When creating an instance from a vxlan tenant network, then attaching an
interface from the vlan provider network, and live migrating, it gives an mtu
error!
2. When creating an instance from a vxlan tenant network, then attaching
an interface from the vlan provider network, hard rebooting the instance
and live migrating, it does not give an mtu error.
3. When creating an instance only from the vlan provider network, it
does not give an mtu error.
4. When creating an instance from the vlan provider network, then
attaching an interface from the vxlan tenant network, and migrating, it
gives an mtu error!
5. When creating an instance, giving an IP from both the vxlan tenant
network and the vlan provider network at the creation time then live
migrating, it does not give an mtu error.
6. When creating an instance only from the vlan provider network, it
does not give an mtu error. Then, when attaching an interface from the
vxlan tenant network and migrating again, it gives an mtu error!
7. Change the vlan provider network mtu from 1500 to 1450. Create a new
instance from vxlan tenant network and then attach a new interface from
vlan provider network. Try live migrate, it gives an mtu error! The
problem is not about the mtu difference between vxlan tenant network and
vlan provider network.
Environment
===========
1. Exact version of OpenStack you are running => Zed installed with
kolla-ansible - Nova Version: 26.2.1.dev2
2. Which hypervisor did you use? => Libvirt + KVM
What's the version of that? => libvirt 8.0.0
3. Which storage type did you use? => Ceph
What's the version of that? => 16.2.7
(dd0603118f56ab514f133c8d2e3adfc983942503) pacific (stable)
4. Which networking type did you use? => Neutron with OpenVSwitch
(openvswitch_agent.ini attached to bug)
Logs & Configs
==============
* Logs and configs attached to bug.
** Affects: nova
Importance: Undecided
Status: New
--
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/2080531
Title:
live migration fails if multi segment networks exist on instance
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
We got the mtu error as below on the source compute node, when live
migrating an instance which have two interface from both vxlan tenant
network and vlan provider networks.
"Target network card MTU 0 does not match source 1450:
libvirt.libvirtError: unsupported configuration: Target network card
MTU 0 does not match source 1450"
Steps to reproduce
==================
1. Create an instance from vlan provider network or vxlan tenant network.
2. Attach the second interface. If instance created with vxlan tenant network
then attach vlan provider network. If instance created with vlan provider
network then attach vxlan tenant network.
3. Try to live migrate the instance.
Expected result
===============
Live migration should be succeded
Actual result
=============
We got the error below on the source compute node (nova-compute)
"Target network card MTU 0 does not match source 1450:
libvirt.libvirtError: unsupported configuration: Target network card
MTU 0 does not match source 1450"
Scenarios
===============
1. When creating an instance from a vxlan tenant network, then attaching an
interface from the vlan provider network, and live migrating, it gives an mtu
error!
2. When creating an instance from a vxlan tenant network, then
attaching an interface from the vlan provider network, hard rebooting
the instance and live migrating, it does not give an mtu error.
3. When creating an instance only from the vlan provider network, it
does not give an mtu error.
4. When creating an instance from the vlan provider network, then
attaching an interface from the vxlan tenant network, and migrating,
it gives an mtu error!
5. When creating an instance, giving an IP from both the vxlan tenant
network and the vlan provider network at the creation time then live
migrating, it does not give an mtu error.
6. When creating an instance only from the vlan provider network, it
does not give an mtu error. Then, when attaching an interface from the
vxlan tenant network and migrating again, it gives an mtu error!
7. Change the vlan provider network mtu from 1500 to 1450. Create a
new instance from vxlan tenant network and then attach a new interface
from vlan provider network. Try live migrate, it gives an mtu error!
The problem is not about the mtu difference between vxlan tenant
network and vlan provider network.
Environment
===========
1. Exact version of OpenStack you are running => Zed installed with
kolla-ansible - Nova Version: 26.2.1.dev2
2. Which hypervisor did you use? => Libvirt + KVM
What's the version of that? => libvirt 8.0.0
3. Which storage type did you use? => Ceph
What's the version of that? => 16.2.7
(dd0603118f56ab514f133c8d2e3adfc983942503) pacific (stable)
4. Which networking type did you use? => Neutron with OpenVSwitch
(openvswitch_agent.ini attached to bug)
Logs & Configs
==============
* Logs and configs attached to bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2080531/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
