websocket API support for stop_mode

Bug #1999152 reported by Peter Makowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Adam Collard

Bug Description

WebSocket machine.action handler for the "off" action is missing support for the stop_mode.

It should support the same parameters that the REST API does.

Example: sending a WebSocket message {"method":"machine.action","type":0,"params":{"action":"off","extra":{ stop_mode: "soft" },"system_id":"6cqq3x"},"request_id":19}

results in an error: "PowerOff._execute() got an unexpected keyword argument 'stop_mode'"

Related branches

Changed in maas:
milestone: none → 3.4.0
importance: Undecided → Medium
status: New → Triaged
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
tags: added: websocket-api
Changed in maas:
milestone: 3.4.x → 3.5.0
status: Triaged → In Progress
assignee: nobody → Adam Collard (adam-collard)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 3.5.0 → 3.5.0-beta1
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.