WebSocket API to report reasons for failure for machine bulk actions

Bug #2009045 reported by Peter Makowski
6
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_system_ids": [ "abc", "def"],
"failure_details": {
  "failed to perform an action x due to y": [ "abc"],
  "another detailed failure message": ["def"],
}

Related branches

Bill Wear (billwear)
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Bill Wear (billwear)
Changed in maas:
milestone: none → 3.4.0
milestone: 3.4.0 → 3.3.1
Bill Wear (billwear)
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
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.0-beta1
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.