initial juju status is really ugly

Bug #1594883 reported by Nate Finch on 2016-06-21
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju
Medium
Anastasia
2.3
Medium
Anastasia

Bug Description

Immediately after you first bootstrap, if you run juju status, you are presented with this wall of text:

$ juju status
MODEL CONTROLLER CLOUD VERSION
default azure azure 2.0-beta10.1

APP STATUS EXPOSED ORIGIN CHARM REV OS

UNIT WORKLOAD AGENT MACHINE PORTS PUBLIC-ADDRESS MESSAGE

MACHINE STATE DNS INS-ID SERIES AZ

$

From a first use perspective, this is really confusing. It's 2 lines of useful information and then 20 words without any context.

IMO, we should elide the column headers for sections that are empty, maybe with [this page intentionally left blank] placeholders.

$ juju status
MODEL CONTROLLER CLOUD VERSION
default azure azure 2.0-beta10.1

[no applications]
[no machines]
$
---- or ----

$ juju status
MODEL CONTROLLER CLOUD VERSION
default azure azure 2.0-beta10.1

This model is empty. Use `juju deploy` to deploy applications to this model. See `juju help deploy` for more details.
$

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
tags: added: usability
affects: juju-core → juju
Anastasia (anastasia-macmood) wrote :

This PR (against 2.3) no longer displays empty sections and will let the user know that the model is empty: https://github.com/juju/juju/pull/8727

Changed in juju:
status: Triaged → In Progress
assignee: nobody → Anastasia (anastasia-macmood)
milestone: none → 2.4-beta3
Anastasia (anastasia-macmood) wrote :

PR against develop (2.4): https://github.com/juju/juju/pull/8729

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers