** Changed in: juju-core
Assignee: (unassigned) = Dimiter Naydenov (dimitern)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https
Proposed a fix with http://reviews.vapour.ws/r/686/ - before starting a
container, the host's primary physical NIC's MTU value is detected and
applied to the container's veth device.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: juju-core
Status: In Progress = Fix Committed
--
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:
Interface MTU management across MAAS/juju
Since 1.23 there's no need to create juju-br0 (or as it used to be
called before - br0) at initial boot, so this should solve the issue.
** Changed in: juju-core
Status: Triaged = Fix Committed
** Changed in: juju-core
Milestone: None = 1.23-beta1
--
You received this bug
See also the related bug 1442257 which has a proposed fix.
--
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:
Interface MTU management across MAAS/juju
Status in
Depending on the version of juju used, one option is to set:
lxc-default-mtu: 9000
in environments.yaml for that environment and re-bootstrap. All LXC
containers juju creates should use 9000 as MTU for the eth0 of the
container.
--
You received this bug notification because you are a member of
juju-br0 was reintroduced in 1.23.3 as the default behavior in MAAS,
unless the address-allocation feature flag is enabled.
AIUI the juju-br0 swallows the interface-mtu DHCP setting coming
from MAAS. It doesn't happen when eth0 is not bound to juju-br0. So it
looks like this is a pre-existing
Additionally, Juju creates bridges on top of both physical and VLAN
interfaces to allow for the same level of addressability for containers
as regular machines. The bridges currently use the "br-" prefix and the
underlying device name, which if it happens to be
"enxxaabbccddeef0.1234" already,
8 matches
Mail list logo