juju debug-log -i unit-rabbitmq-server-0 is unfriendly
Bug #1576851 reported by
Adam Stokes
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Tim Penhey | ||
Bug Description
Everywhere else you reference a unit with 'rabbitmq-server/0' except for when wanting to filter out units in debug-log.
Currently you have to type:
juju debug-log -i unit-rabbitmq-
Which is inconsistent with how you access the unit with other cli commands, ie juju ssh rabbitmq-server/0
| description: | updated |
Revision history for this message
| Cheryl Jennings (cherylj) wrote | #1 |
| tags: | added: debug-log juju-release-support |
| tags: | added: usability |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
| Changed in juju-core: | |
| milestone: | none → 2.0.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| John A Meinel (jameinel) wrote | #3 |
| Changed in juju: | |
| assignee: | nobody → Tim Penhey (thumper) |
| milestone: | none → 2.2.1 |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I could've sworn I already saw a bug for this, but I cannot find anything in lp.