1.21b3: juju status isn't filtering by service
Bug #1397995 reported by
Andreas Hasenack
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Katherine Cox-Buday | ||
1.21 |
Fix Released
|
Critical
|
Katherine Cox-Buday |
Bug Description
juju-core 1.21 beta3 is the first version in the 1.21 series that I have tried, so I don't know when this changed.
The juju status output no longer seems to filter by service. Now, when I do a "juju status <service>", I get information about all the other services in the output. In 1.20.13, I only get the service I requested.
Attached are juju status outputs of the same deployment with juju 1.20 and 1.21b3.
Changed in juju-core: | |
status: | New → Triaged |
status: | Triaged → New |
Changed in juju-core: | |
milestone: | none → 1.21 |
Changed in juju-core: | |
milestone: | 1.21 → 1.22 |
tags: | added: status |
Changed in juju-core: | |
assignee: | nobody → Katherine Cox-Buday (cox-katherine-e) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This must be a server issue because the beta3 is showing the correct info when talking to a 1.20.x env 10.245. 67.134 jenkins- slave-14
agent- state: started
agent- version: 1.20.13
public- address: 10.245.67.134
juju status ppc*
environment: juju-ci3
machines:
"36":
agent-state: started
agent-version: 1.20.13
dns-name: 10.245.67.134
instance-id: manual:
series: trusty
hardware: arch=ppc64 cpu-cores=1 mem=8166M
services:
ppc-slave:
charm: local:trusty/
exposed: false
relations:
slave:
- jenkins
units:
ppc-slave/0:
machine: "36"