Update status_message to include latest "Mark broken" message
Bug #1871003 reported by
Caleb Ellis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Dougal Matthews | ||
Bug Description
Zeplin wireframe: https:/
The new design for the "Mark broken" action proposes allowing the user to leave a message as to why the selected machines are being marked broken. That message is then surfaced in the machine list under Status.
To make this work we need:
- The `mark-broken` websocket method to accept a message parameter
- To update machine.
Related branches
~d0ugal/maas:mark-broken-messsage
- Alberto Donato (community): Approve
- MAAS Lander: Needs Fixing
-
Diff: 40 lines (+13/-3)2 files modifiedsrc/maasserver/node_action.py (+2/-2)
src/maasserver/tests/test_node_action.py (+11/-1)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Medium → High |
| assignee: | nobody → Dougal Matthews (d0ugal) |
| Changed in maas: | |
| milestone: | 2.8.0b1 → 2.8.0b2 |
| Changed in maas: | |
| status: | Triaged → In Progress |
Revision history for this message
| Alberto Donato (ack) wrote | #1 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Caleb Ellis (caleb-ellis) wrote | #2 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
@Caleb is machine.
That seems to be more a message for event logs, as currently it would show something like:
"User marking node broken - (user@domain) - <user-provided message>"
Is that what's desired?
If only the message that the user provided is desired, that should be machine.