@James,
the bug was incomplete because the question in comment #2 was never
answered until comment #4.
So it sounds like something juju needs to do through lxc config - if
there is anything sane that you can think of htat lxc can do to help,
please let us know.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
LXC containers reset bridge MTU on start/restart
Status in juju-core:
Triaged
Status in MAAS:
Incomplete
Status in “lxc” package in Ubuntu:
Invalid
Bug description:
Context:
juju + MAAS deployed OpenStack environment, misc services deployed
under LXC on the bootstrap node, interfaces configured for jumbo
frames - note that I had to manually set the LXC container interfaces
to mtu 9000 before the bridge would do the same.
Action:
Reboot one of the containers; MTU on br0 resets from 9000 -> 1500.
This feels like more of a 'we need a better way to orchestrate MTU
configuration across different services' so raising tasks for MAAS and
Juju as well.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.5-0ubuntu0.1
ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
Date: Tue Aug 12 13:26:00 2014
KernLog:
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
lxcsyslog:
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
