Description of problem:
Often a larger number of systems get marked broken, due to the way we track this it is easy enough to build a hostlist.
It would be awesome if one could perform administrative tasks against a system in beaker via the command line.
In particular, it would be very handy if one was able to set a system back to 'Automated' via bkr. It is anticipated that this action will also be noted in the systems history tab.
Version-Release number of selected component (if applicable):
This would be an improvement upon using sql statements file generated by intermediate scripts or manipulating via csv export/modify/import.
Optionally an alias for marking the system as unbroken could be implemented, and it would revert the status to that before it was last marked broken.
*** Bug 840556 has been marked as a duplicate of this bug. ***
Bulk reassignment of issues as Bill has moved to another team.
As per bug 1037592, this is currently referred to as the system Condition in the web UI (although the system search options still refer to it as "Status").
However, we're not completely happy with the current condition modelling, so I'd prefer to revisit that before adding a command line interface for it.
*** Bug 1119930 has been marked as a duplicate of this bug. ***
We do still need to deal with the issues around Condition/Status (bug 1039842) but we won't hold up this RFE for that.
Beaker 19.0 has been released.