Targeting 0.15.3, since the UI upgrade is likely to break any existing scripts that are scraping the HTML for this info.

We'll look into two options for this:

1. Adding more info to the output of "bkr system-details"
2. Adding a new "bkr system-status" command

Option 1 seems more likely at this point, but option 2 is a possibility if there turns out to be some technical reason that option 1 isn't a good idea after all.

The bkr system-details command is for hardware details and other physical properties that don't normally change over time. A separate command for querying system reservations would be a better choice.

In that case, here's the info I think we should include for a new "bkr system-status" command:

- current condition (automated, manual, broken, removed)
- power type (if any)
- current reservation (if any)
- current loan (if any)

Including the power type is mostly to pick up cases where a system is "Automated", but doesn't have automatic power control configured.

In the future, we may also want to support something like:

    bkr system-reservations --current
    bkr system-loans --current

But that CLI making sense depends on tracking historical data for reservations and loans directly (so they can be listed over time), whereas the system-status command would just be about providing a snapshot of the current state of the system.

I think bkr system-status is a bad name because status is already used when designating a system as 'Automated', 'Broken' etc.
(In reply to Nick Coghlan from comment #5)
> In that case, here's the info I think we should include for a new "bkr
> system-status" command:
> 
> - current condition (automated, manual, broken, removed)
> - power type (if any)
> - current reservation (if any)
> - current loan (if any)
> 
> Including the power type is mostly to pick up cases where a system is
> "Automated", but doesn't have automatic power control configured.
> 

This seems out of place and a gateway option for further scope creep. Should bkr list-systems not be used for filtering on such things ?

> In the future, we may also want to support something like:
> 
>     bkr system-reservations --current
>     bkr system-loans --current
> 
> But that CLI making sense depends on tracking historical data for
> reservations and loans directly (so they can be listed over time), whereas
> the system-status command would just be about providing a snapshot of the
> current state of the system.

As noted on bug 1039842, the system details paged currently uses "Condition", rather than Status for the automated/manual/broken/removed setting.

I think it's better to use "Status" in the more general sense, and start working towards using "Condition" more consistently for the narrow sense.

Agreed on leaving out the power type information, though.

*** Bug 783565 has been marked as a duplicate of this bug. ***

When this fix is ready, will it also fix BZ#858723 ?

Ray's patch on Gerrit: http://gerrit.beaker-project.org/#/c/2614/

*** Bug 858723 has been marked as a duplicate of this bug. ***

This change is included in the Beaker 0.15.3 maintenance release:

http://beaker-project.org/docs/whats-new/release-0.15.html#beaker-0-15-3

Yeah, I had the same problem while I was working for a loan app a long time ago. When a user sends a request to us we will get only errors with a message. That was a problem because we couldn’t work properly and would not understand if he is clicking on a right page here https://play.google.com/store/apps/details?id=com.payday.advance.money.loan&hl=en_US&gl=US and if he is trying to get personal loan via our link or it is link from some other apps that are available on a market. We spend a lot of time dealing with that problem and it was really hard because the main point is to find a place where we get that mistake. Right now this app is working properly and we are getting money from them easily and without problems, users are also ok with it.