machine.action does not always throw errors for failed machines

Bug #1991795 reported by Peter Makowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned

Bug Description

Currently the websocket API responds to machine.action performed with a filter only with a number of nodes that the action was performed on successfully, even if an action could not be performed on some of the nodes requested (e.g. when trying an action that's not supported, like test on a machine that's already being tested).

request: request_id: 25, method: "machine.action", params: {action: "test", filter: {id: ["tw8pfr", "b3ye4t"]}}

response: { request_id: 25, result: 1 }

We need either an error message or a list of failed machines to be added to the response (system_ids/names).

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → High
Changed in maas:
milestone: none → 3.3.0
status: Triaged → Fix Committed
Changed in maas:
milestone: 3.3.0 → 3.3.0-beta1
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.