juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
juju-core |
Fix Released
|
High
|
Andrew McDermott | ||
1.25 |
Fix Released
|
High
|
Andrew McDermott |
Bug Description
MAAS 1.9 introduced support for bonding of network interfaces. When juju deployes a machine with such an interface, it creates juju-br0 on top of bond0. However, it doesn't do this properly.
Instead of creating juju-br0 and taking ownership of layer3 properties (IP address, gateway), juju-br0 fully replaces bond0. This leads to a configuration in /etc/network/
auto juju-br0
iface juju-br0 inet static
address a.b.c.d/24
gateway a.b.c.f
bridge-port bond0
bond-mode active-backup
<other bonding properties>
While this isn't terribly wrong (it should still work), problem is that juju-br0 *replaces* bond0. This leads to a problem where bond0 is marked as bridge-port, but bond0 is nowhere to be defined in /etc/network/
I can easily reproduce this with MAAS 1.9, by creating a bond interfaces that use the same bond, but different VLANs (bond0 bond0.10 for example). Unfortunately, I managed to delete /etc/network/
Changed in juju-core: | |
milestone: | 1.25.1 → 1.25.2 |
Changed in juju-core: | |
assignee: | nobody → Andrew McDermott (frobware) |
Changed in juju-core: | |
milestone: | 1.25.2 → 1.26-beta1 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 1.26-beta1 → 2.0-alpha1 |
Changed in juju-core: | |
milestone: | 2.0-alpha1 → 1.26-alpha3 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
This does not seem to be a MAAS bug, since MAAS simply calls curtin to create the proper /etc/network/ interfaces. So I'm marking this 'Invalid' for MAAS. Please adjust as necessary if it turns out a MAAS change is needed.