juju status tabular format doesn't show controller member status

Bug #1585059 reported by Brad Marshall
This bug report is a duplicate of:  Bug #1575310: Add "juju status --verbose".. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Confirmed
High
Unassigned

Bug Description

With juju-2.0 beta 7 (and earlier versions) there is no indication in the tabular format version of juju status which machines are controller members / state servers. For example, with juju status --format=yaml:

machines:
  "0":
    juju-status:
      current: started
      since: 24 May 2016 00:16:47-04:00
      version: 2.0-beta7
    dns-name: 10.48.0.14
    instance-id: node-8d3677b2-de9c-11e5-b062-ecb1d78a2580
    machine-status:
      current: running
      message: Deployed
      since: 24 May 2016 00:04:50-04:00
    series: xenial
    hardware: arch=amd64 cpu-cores=1 mem=32768M tags=infra,virtual,bootstrap availability-zone=default
    controller-member-status: has-vote

But with juju status --format=tabular:

0 started 10.48.0.14 node-8d3677b2-de9c-11e5-b062-ecb1d78a2580 xenial default

This means I have to flip back and forth between juju status types to see different bits.

If there was some way to convey this information about what is a controller / state server in the tabular output it would be very useful.

Changed in juju-core:
milestone: none → 2.0.0
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Ian Booth (wallyworld) wrote :

We need to be careful here - tabular status was designed to be the end user view into their model. And end users who deploy workloads on a controller they have a model in but which they did not bootstrap don't care about such things as mongo replicaset details. We need to be careful about cluttering status any more than it already is for the primary use case. Maybe a non-default option to status could be considered for displaying extra, low level information.

Revision history for this message
Brad Marshall (brad-marshall) wrote :

The extra, non-default option could work, it'd be good to not have to flip to a different format to find the information I need for this. The tabular format is getting better all the time, so the more I can use it and stay away from yaml, the better.

Revision history for this message
Cheryl Jennings (cherylj) wrote :

There is already a bug to add something like juju status --verbose to output additional information. I'll add in the member status to that bug as something else to display as part of verbose output.

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.