1.8beta1: Attempting to release a node that's already releasing results in an error
Bug #1442807 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
ubuntudotcom1 | ||
Bug Description
If I try to release a node that's already in Releasing state, I get an error back from the API. This should be a no-op and shouldn't return an error.
"Node cannot be released in its current state ('Releasing')."
Related branches
lp://qastaging/~ubuntudotcom1/maas/bug-1442807-release-releasing-node-results-in-error
- Blake Rouse (community): Approve
- Mike Pontillo (community): Approve
-
Diff: 40 lines (+9/-3)2 files modifiedsrc/maasserver/api/nodes.py (+4/-2)
src/maasserver/api/tests/test_node.py (+5/-1)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.8.0 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Incomplete |
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote | #2 |
| Changed in maas: | |
| status: | Incomplete → Triaged |
| Changed in maas: | |
| assignee: | nobody → ubuntudotcom1 (ubuntudotcom1) |
| tags: | added: cli |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Jason,
Is this still the case in the latest beta? (berta6)?