After "mark broken" and "mark fixed" it's no longer possible to mark the machine broken again

Bug #1889026 reported by Kit Randel
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned

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://github.com/canonical-web-and-design/maas-ui/issues/1369
Reported by: gianlucagiacometti (https://github.com/gianlucagiacometti)

Related branches

Kit Randel (blr)
description: updated
Revision history for this message
Bill Wear (billwear) wrote :

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.

Changed in maas:
status: New → Triaged
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
Revision history for this message
Adam Collard (adam-collard) wrote :

Overall, the state transitions are a bit broken here - let's do a targetted fix for 3.5 whilst avoiding a re-write.

Changed in maas:
assignee: Igor Brovtsin (igor-brovtsin) → nobody
status: In Progress → Triaged
milestone: none → 3.5.0
Changed in maas:
milestone: 3.5.0 → 3.5.x
no longer affects: maas/3.4
no longer affects: maas/3.3
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.