LXD VM hosts can't be refreshed if VLANs interfaces aren't named $parent.$vid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Björn Tillenius | ||
3.0 |
Fix Released
|
High
|
Björn Tillenius |
Bug Description
This is with MAAS 3.0.0~rc1.
Register a LXD VM host that has a VLAN interface that isn't name like eth1.123 (parent name and vid), e.g. myvlan.
If you refresh the LXD VM host, it will stall.
If you look in the logs, you'll see that the metadata server return a 409 Conflict.
The reason for that is that we have code VLANInterface that ignores the given name, unless it's a controller.
update_
VLANInterface.
The first time that code runs it works, since there is no eth1.123. But the second time, eth1.123 already exists, so the unique (node, interface_name) is triggered.
Related branches
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 79 lines (+27/-16)2 files modifiedsrc/maasserver/models/interface.py (+9/-16)
src/metadataserver/builtin_scripts/tests/test_network.py (+18/-0)
Changed in maas: | |
milestone: | none → 3.0.1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Björn Tillenius (bjornt) |
milestone: | 3.0.1 → none |
status: | Triaged → In Progress |
Changed in maas: | |
milestone: | none → 3.0.0 |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.0.0 → none |
Changed in maas: | |
milestone: | none → 3.2.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |