Maas api /machines/{system_id}/?op=restore_networking_configuration does not clear network config
Bug #1687420 reported by
Tom Mullaney
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Björn Tillenius | ||
Bug Description
Maas api /machines/
I also tried to use /machines/
The storage layout was reset, but the network config remained intact.
I am using MAAS 2.2.0~rc2 (bzr5922-0ubuntu1)
To recreate the bug just create a node in maas, add a bond then run the api function for /machines/
My expected result is the node to go back to the same state as directly after commissioning. If this assumption is wrong please let me know.
Related branches
lp://qastaging/~bjornt/maas/reset-network-config
- Mike Pontillo (community): Approve
-
Diff: 343 lines (+115/-17)7 files modifiedsrc/maasserver/api/machines.py (+2/-0)
src/maasserver/api/tests/test_machine.py (+6/-0)
src/maasserver/models/node.py (+14/-0)
src/maasserver/models/tests/test_node.py (+73/-1)
src/metadataserver/builtin_scripts/hooks.py (+8/-3)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+7/-12)
src/provisioningserver/refresh/node_info_scripts.py (+5/-1)
| Changed in maas: | |
| milestone: | none → 2.2.0rc4 |
| Changed in maas: | |
| assignee: | nobody → Björn Tillenius (bjornt) |
| Changed in maas: | |
| status: | New → In Progress |
| Changed in maas: | |
| milestone: | 2.2.0rc4 → 2.2.0rc5 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| milestone: | 2.2.0rc5 → 2.2.0 |
To post a comment you must log in.
