[2.5] Machine subnet links removed after release after deployment using bridge_all=true
Bug #1792409 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mike Pontillo |
Bug Description
I used a command like the following to deploy a machine, using the bridge_all option so that MAAS would know about the bridge interfaces:
maas admin machine deploy xy1z23 user_data="$(base64 ~/userdata -w 0)" bridge_all=true
This worked fine for the deployment, but when the machine was released, the bridge was removed along with its subnet link. Thus, subsequent deployments did not work, because the node was "not connected to a network".
Related branches
~mpontillo/maas:prevent-ip-removal-on-bridge-release--bug-1792409
Merged
into
maas:master
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 17 lines (+5/-1)1 file modifiedsrc/maasserver/models/node.py (+5/-1)
summary: |
- [2.5] Machine subnet links removed after release when deployed using + [2.5] Machine subnet links removed after release after deployment using bridge_all=true |
Changed in maas: | |
milestone: | 2.5.0beta2 → 2.5.0rc1 |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0beta4 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
After further testing I can't reproduce this, so marking Incomplete for now.