1.21b3: juju status isn't filtering by service

[Andreas Hasenack]

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.

[Curtis Hovey (sinzui)]

This must be a server issue because the beta3 is showing the correct info when talking to a 1.20.x env
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:10.245.67.134
    series: trusty
    hardware: arch=ppc64 cpu-cores=1 mem=8166M
services:
  ppc-slave:
    charm: local:trusty/jenkins-slave-14
    exposed: false
    relations:
      slave:
      - jenkins
    units:
      ppc-slave/0:
        agent-state: started
        agent-version: 1.20.13
        machine: "36"
        public-address: 10.245.67.134

[Andreas Hasenack (ahasenack)]

Just to be clear, when I said:

"Attached are juju status outputs of the same deployment with juju 1.20 and 1.21b3."

I meant the same app was deployed, but once with 1.20 and then with 1.21b3, destroying the environment each time.

[Katherine Cox-Buday (cox-katherine-e)]

It looks like a good start would be to backport the fix to this: https://bugs.launchpad.net/juju-core/+bug/1385456

We erroneously believed this had been brought over to the v1.21 series. There is no guarantee that it will fix your issue, but it's certainly a contributing factor and will allow us to take the next step in diagnosis.

[Katherine Cox-Buday (cox-katherine-e)]

This has been backported to v1.21. Can you please try your use-case again and let me know if it's more appropriate?

[Andreas Hasenack (ahasenack)]

Sorry, I need a binary ;)

[Andreas Hasenack (ahasenack)]

Got the binary and the fix is correct, the principal service filtering is now working. There is extra output about the subordinates, but that's working as designed and is out of scope for this bug.