After "mark broken" and "mark fixed" it's no longer possible to mark the machine broken again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
In Progress
|
Medium
|
Igor Brovtsin | ||
3.3 |
Won't Fix
|
Medium
|
Igor Brovtsin | ||
3.4 |
Triaged
|
High
|
Igor Brovtsin |
Bug Description
After marking a machine "broken", and then "fixed", it's no longer possible to mark the machine broken again. At the same time the status of the machine after fixing does not come back to its original name (i.e. Ubuntu 18.04), but becomes "Deployed".
# MAAS version
2.8.1
# To Reproduce
Steps to reproduce the behavior:
Mark a machine broken
Mark it fixed
The Status changes to "Deployed"
Mark "broken" is no longer available as a machine action (confirmed on bolla by inspecting the machines `actions` property).
# Expected behaviour
It should be possible to re-iterate the mark broken - mark fixed as many times as needed.
Original gh bug: https:/
Reported by: gianlucagiacometti (https:/
Related branches
- Björn Tillenius: Disapprove
- Adam Collard (community): Needs Fixing
- MAAS Lander: Approve
-
Diff: 16 lines (+0/-5)1 file modifiedsrc/maasserver/node_action.py (+0/-5)
description: | updated |
Changed in maas: | |
importance: | Undecided → Medium |
milestone: | none → 3.3.0 |
Changed in maas: | |
assignee: | nobody → Igor Brovtsin (igor-brovtsin) |
Changed in maas: | |
milestone: | 3.3.0 → 3.4.0 |
summary: |
- After "mark broken" and "mark fixed" it's no more possible to mark the + After "mark broken" and "mark fixed" it's no longer possible to mark the machine broken again |
Changed in maas: | |
milestone: | 3.3.0 → none |
description: | updated |
Independently confirmed. If machine is in "Depoloyed" state, you can mark it broken, then mark it fixed. The next time you choose the "Take action" menu, the menu will not present "Mark broken" for that machine. If you select all deployed machines, the count for "Mark broken" will be one less, excluding that one machine. If you attempt to mark all deployed machines broken at this point, MAAS will refuse, asking you to update your selection as "1 machine cannot be marked broken" -- but it doesn't tell you which one, it's now a guessing game.