[2.2] After aborting a deployment, the machine cannot be deployed via the CLI
Bug #1680886 reported by
Brendan Donegan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Mike Pontillo | ||
Bug Description
If we Abort a deployment then the machine transitions to the Allocated state, from which it should be possible to deploy it. However this is not possible via the CLI/API - a 400 error is returned. Selecting Deploy via the UI still works however.
Related branches
lp://staging/~mpontillo/maas/fix-redeploy-aborted-deployment-api--bug-1680886
- Blake Rouse (community): Approve
-
Diff: 66 lines (+32/-13)2 files modifiedsrc/maasserver/api/machines.py (+12/-13)
src/maasserver/api/tests/test_machine.py (+20/-0)
| Changed in maas: | |
| importance: | Undecided → High |
| milestone: | none → 2.2.0 |
| milestone: | 2.2.0 → 2.2.0rc2 |
| importance: | High → Critical |
| Changed in maas: | |
| status: | New → Triaged |
| Changed in maas: | |
| assignee: | nobody → LaMont Jones (lamont) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| assignee: | LaMont Jones (lamont) → nobody |
| status: | In Progress → Triaged |
| Changed in maas: | |
| milestone: | 2.2.0rc2 → 2.2.0rc3 |
| Changed in maas: | |
| assignee: | nobody → Mike Pontillo (mpontillo) |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
