>From James's duplicate bug:
In our MAAS based openstack deployment, we provide MTU via DHCP to all
servers to enable jumbo frames.
This works fine until juju creates the bridge devices for LXC or KVM
containers, at which point we reliably lose the MTU 9000 setting on the
bridge, resulting in all sorts of MTU related fun in things like
corosync and percona-cluster which are running under lxc.
We've fixed this by appending an explicit mtu set to the bridge
definition in /etc/network/interfaces:
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0
post-up /sbin/ip link set eth0 mtu 9000
After making this change, we can reliably reboot physical hosts
container lxc containers, an not break our clusters.
The issue is that MTU has to be set on the underlying device, not the
bridge itself - this may actually be something we can fix in the
dhcpclient tools
** Changed in: juju-core
Status: Invalid => Triaged
** Changed in: juju-core
Importance: Undecided => Medium
** Tags added: kvm lxc network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
interface br0
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
