Host veth mtu not preserved during container reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
lxc (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
LXC containers configured with lxc.network.mtu = 9000
On start/restart using lxc-* commands, the mtu on the host and in container interface is correctly set to 9000.
However, if the container is rebooted internally, the mtu of the veth on the host resets to 1500, whilst the container interface is still set to 9000.
This causes some odd network behaviour.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.6-0ubuntu0.1 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Thu Dec 11 20:34:27 2014
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
tags: | added: landscape smoosh |
Was not able to reproduce this on my utopic host or a trusty VM. James will try to come up with a reproducer.