In 3.5 when I release a machine with the 'erase disk option' the disk is actually not erased
Bug #2060687 reported by
Jacopo Rota
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Committed
|
High
|
Jacopo Rota | ||
| 3.5 |
Fix Committed
|
High
|
Jacopo Rota | ||
Bug Description
In 3.5 if I release a machine with the 'erase disk option' the disk is actually not erased. Steps to reproduce:
1) deploy a machine
2) release a machine and enable the 'erase disk option'.
3) disable dhcp on the subnet
4) start the machine manually -> it boots from the disk as it was not erased
Related branches
~r00ta/maas:lp-2060687-3.5
- Jacopo Rota: Approve
-
Diff: 46 lines (+12/-3)2 files modifiedsrc/metadataserver/api.py (+4/-1)
src/metadataserver/tests/test_api.py (+8/-2)
~r00ta/maas:lp-2060687
- MAAS Lander: Approve
- Stamatis Katsaounis: Approve
-
Diff: 46 lines (+12/-3)2 files modifiedsrc/metadataserver/api.py (+4/-1)
src/metadataserver/tests/test_api.py (+8/-2)
Revision history for this message
| Jacopo Rota (r00ta) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Jacopo Rota (r00ta) |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
