Release nodes doesn't release any if one is not found
Bug #1392225 reported by
Michael Foord
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
An inconsistency within "/api/1.0/nodes/ op=release", if one of the nodes is in conflict (error 409) then the others will still be released. If a node is missing, or there is a permission error on one, then the other nodes are not released.
| tags: | added: api papercut |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Hi!
We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.
Thanks