** Changed in: juju-core
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being
** Tags removed: sts sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
interface
** Changed in: juju-core
Milestone: 1.23-beta1 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being
The bug is still present in 1.25.
The fact that it only manifests itself during the subsequent machine
reboots (and not during the initial build) makes it more difficult to
troubleshoot - services that worked before reboot do not work after.
--
You received this bug notification because you are
** Tags removed: cts
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
This issue is still a problem in 1.23, we just reproduced it.
Also, not sure why this bug was marked as fix released when there was no
fix to release, just the assumption that this problem would not happen
due to some new condition that doesn't seem to be met by our environment
either. I think in
** Changed in: juju-core
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being
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
The fix should check if the phys interface MTU lxc-default-mtu, then
enforce the MTU on the phys interface or apply the 'post-up /sbin/ip
link set eth0 mtu 9000', entry on the juju-br0 config.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
We have tried to use the option lxc-default-mtu: 9000, on juju version
1.23.3 and did the following:
1) bootstrap to a machine
2) create an lxc containter on the bootstrap node
3) deploy ubuntu to another lxc container on the same node
The option didn't have any effect. All the interfaces ended
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Changed in: juju-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is
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
Hi Robie,
Let me answer your questions:
Why is br0 being set up to bridge eth0? Is something doing this automatically
or is this configuration necessary for something (if so, what?)?
This configuration (br0 on a single physical interface) is automatically
generated by deploying openstack
Presumably this is related to the DHCP client via dhclient and dhclient-
script, so presumably should be a task on isc-dhcp?
I see code in dhclient-script that sets the MTU based on the DHCP
option, but it doesn't have any special behaviour for br0. So I'm
wondering if this code is being used at
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1355813/comments/3
might be relevant here. Kapil says: ...you can't really set a bridge
mtu, you have to set it for all the containers on the bridge, ie.
bridges take the lowest mtu of their interfaces. so instead we have to
set all the containers
21 matches
Mail list logo
