Bridges without parents are not modeled after rack controller registers
Bug #1570104 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo |
Bug Description
I set up a test system with the following bridge configuration:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.525400130e6f no ens3
br1 8000.000000000000 no
virbr0 8000.5254005caca1 yes virbr0-nic
As you can see, br0 is the only bridge interface linked to a physical interface. It is also the only bridge interface that appears under the controller in MAAS after the rack registers.
Now that LXD does not depend on lxcbr0, it would be good if rack registration considers all bridges, not just bridges linked only to a physical interface.
Related branches
lp:~mpontillo/maas/fix-bridge-registration-1570104
- Blake Rouse (community): Approve
-
Diff: 266 lines (+116/-22)5 files modifiedsrc/maasserver/models/interface.py (+14/-8)
src/maasserver/models/node.py (+32/-10)
src/maasserver/models/tests/test_node.py (+60/-0)
src/maasserver/tests/test_preseed_network.py (+2/-2)
src/provisioningserver/utils/network.py (+8/-2)
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Changing the priority to critical provided that this is affecting local testing.