Add ability to view errors in juju status

Bug #1727639 reported by Sandor Zeestraten
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Jon Seager

Bug Description

It would be nice if juju had some way to show errors in the status output for those of us with somewhat large models.

With a small HA OpenStack, the `juju status` output is 375 lines long and hunting for charm errors can be a bit annoying.

Something like `juju status --errors` or `juju show-errors`.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

We have had conversation about exposing errors in a more obvious way. Thank you for filing a bug \o/

Meanwhile, 'juju status --format=yaml' shows errors.

We cannot put the errors in standard, tabular format of 'juju status' as the errors have tendency to be verbose.

Changed in juju:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: usability
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1727639] [NEW] Add ability to view errors in juju status

You can do:
  juju status error

Which will only show units with 'error' as a status (or potentially also an
application named status).
It doesn't, however, consider 'blocked' or some other types of status as
'error' as it is just a string match.

On Thu, Oct 26, 2017 at 12:01 PM, Sandor Zeestraten <email address hidden>
wrote:

> Public bug reported:
>
> It would be nice if juju had some way to show errors in the status
> output for those of us with somewhat large models.
>
> With a small HA OpenStack, the `juju status` output is 375 lines long
> and hunting for charm errors can be a bit annoying.
>
> Something like `juju status --errors` or `juju show-errors`.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1727639
>
> Title:
> Add ability to view errors in juju status
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1727639/+subscriptions
>

Revision history for this message
Sandor Zeestraten (szeestraten) wrote :

Aha, that is exactly what I'm looking for.

Reading the `juju status --help` output, I got the impression that it only would match on applications, units and machines so I did not even think of trying it.

Details:
By default (without argument), the status of the model, including all
applications and units will be output.

Application or unit names may be used as output filters (the '*' can be used as
a wildcard character). In addition to matched applications and units, related
machines, applications, and units will also be displayed. If a subordinate unit
is matched, then its principal unit will be displayed. If a principal unit is
matched, then all of its subordinates will be displayed.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

As per comments above, we should update command help for clarity.

Changed in juju:
importance: Wishlist → Medium
tags: added: helpdocs
tags: added: helptext
removed: helpdocs
Alvaro Uria (aluria)
tags: added: canonical-bootstack
Revision history for this message
Jon Seager (jnsgruk) wrote :
Changed in juju:
assignee: nobody → Jon Seager (jnsgruk)
milestone: none → 2.9.31
status: Triaged → In Progress
Jon Seager (jnsgruk)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
milestone: 2.9.31 → 2.9.30
milestone: 2.9.30 → 2.9.31
Changed in juju:
status: Fix Committed → Fix Released
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.