juju status tabular format doesn't show controller member status
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-
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,
controller-
But with juju status --format=tabular:
0 started 10.48.0.14 node-8d3677b2-
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 |
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.