touch-packages team mailing list archive

[Serge Hallyn <1401658@xxxxxxxxxxxxxxxxxx>]

So the problem for you is that juju creates the containers with the
wrong mtu?

I don't know where juju gets its config file, (that it passes to 'lxc-
create -f" but the best solution appears to be to update that to set the
mtu before the containers are ever created.

** Also affects: juju (Ubuntu)
   Importance: Undecided
       Status: New

** 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/1401658

Title:
  Host veth mtu not preserved during container reboot

Status in juju package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  Invalid

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/lxc/config/ubuntu.common.conf]
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1401658/+subscriptions