mtu configuration should not be moved to bridge interface
Bug #1584616 reported by
Trent Lloyd
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Andrew McDermott | ||
juju-core |
Won't Fix
|
High
|
Michael Foord | ||
1.25 |
Fix Released
|
High
|
Michael Foord |
Bug Description
When deploying juju 2.0-beta7 onto a xenial machine managed by MAAS 2, the mtu statement is moved from the interface to the bridge.
The MTU statement must be on the interface to work, as bridges inherit the lowest MTU of all sub-interfaces.
Further to this, ifupdown seems to bug out and always fails to add the default route when an MTU is set on the bridge. Thus, this issue completely breaks the network on reboot.
tags: | added: blocker |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
tags: | removed: blocker |
tags: | added: 2.0 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta12 → none |
milestone: | none → 2.0-beta12 |
Changed in juju-core: | |
assignee: | nobody → Michael Foord (mfoord) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in juju-core: | |
status: | In Progress → Won't Fix |
To post a comment you must log in.
The following bug is partially related, but is technically for a different issue: /bugs.launchpad .net/juju- core/+bug/ 1403955
https:/