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
>
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: /bugs.launchpad .net/bugs/ 1727639 /bugs.launchpad .net/juju/ +bug/1727639/ +subscriptions
>
> 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:/
>
> Title:
> Add ability to view errors in juju status
>
> To manage notifications about this bug go to:
> https:/
>