WebSocket API to report reasons for failure for machine bulk actions
Bug #2009045 reported by
Peter Makowski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Igor Brovtsin | ||
| 3.3 |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
When machine action performed from the machine page fails, the error message does not report the reason for the failure.
There can be multiple reasons for failure for subsets of machines, I'd suggest that on top of the existing response we add a new key that will allow us to understand the reasons for which each machine failed and making it actionable.
Something along these lines:
"failed_
"failure_details": {
"failed to perform an action x due to y": [ "abc"],
"another detailed failure message": ["def"],
}
Related branches
~igor-brovtsin/maas:report-bulk-action-errors
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 77 lines (+16/-5)2 files modifiedsrc/maasserver/websockets/handlers/machine.py (+11/-5)
src/maasserver/websockets/handlers/tests/test_machine.py (+5/-0)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in maas: | |
| milestone: | none → 3.4.0 |
| milestone: | 3.4.0 → 3.3.1 |
| Changed in maas: | |
| milestone: | 3.3.1 → 3.4.0 |
| milestone: | 3.4.0 → 3.3.x |
| milestone: | 3.3.x → 3.4.0 |
| Changed in maas: | |
| assignee: | nobody → Igor Brovtsin (igor-brovtsin) |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
