show-status-log formatting contains unwanted pad lines

Bug #1661576 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned
2.0
Won't Fix
Undecided
Unassigned

Bug Description

It appears that each line of output from show-status-log is padded with whitespace at the end, so all line lengths match the longest entry. This messes up formatting, where I end up with extra lines of whitespace between entries because one of them contained a rather long status message. Work around is to pipe the output though something that strips the trailing whitespace ('juju show-status-log postgresql/72 | col -b').

TIME TYPE STATUS MESSAGE
03 Feb 2017 16:47:57+07:00 workload waiting waiting for machine

03 Feb 2017 16:47:57+07:00 juju-unit allocating

03 Feb 2017 16:49:44+07:00 workload waiting installing agent

03 Feb 2017 16:49:47+07:00 workload waiting agent initializing

03 Feb 2017 16:49:48+07:00 workload maintenance installing charm software

03 Feb 2017 16:49:49+07:00 juju-unit executing running install hook

03 Feb 2017 16:53:27+07:00 workload maintenance Updating apt cache

03 Feb 2017 16:53:33+07:00 workload maintenance Installing postgresql-9.5,postgresql-client-9.5,postgresql-client-common,postgresql-common,postgresql-contrib-9.5,python3-psycopg2,run-one
03 Feb 2017 16:54:38+07:00 workload maintenance Starting PostgreSQL

03 Feb 2017 16:54:43+07:00 workload active Live master (9.5.5)

03 Feb 2017 16:54:45+07:00 juju-unit executing running leader-elected hook

03 Feb 2017 16:54:48+07:00 workload active Live master (9.5.5)

03 Feb 2017 16:54:48+07:00 juju-unit executing running config-changed hook

03 Feb 2017 16:54:52+07:00 workload active Live master (9.5.5)

03 Feb 2017 16:54:52+07:00 juju-unit executing running start hook

03 Feb 2017 16:54:55+07:00 workload active Live master (9.5.5)

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

@Stuart,
Please clarify what version of Juju you are running.

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Stuart Bishop (stub) wrote :

2.0.2-xenial-amd64

Changed in juju-core:
status: Incomplete → New
Revision history for this message
Anastasia (anastasia-macmood) wrote :

We track Juju 2.x issues in "juju" project. Re-targeting :D

no longer affects: juju-core
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marking as Won't Fix for 2.0.x as we are not planning another Juju 2.0.x release.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: usability
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
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.