John,

That does not explain why the output of juju status <application> for the
same application would, from run to run, show a different set of services.

On Wed, Apr 12, 2017 at 6:08 AM, John A Meinel <email address hidden>
wrote:

> I believe the logic is probably consistent, if unexpected. I believe
> what actually happens when you type "juju status foo" is that we find
> applications named foo, find the units of the application, then find the
> machines where those units are running, and then display all of the
> information about those machines (including other applications that are
> running on those machines).
>
> The reason 'juju status rabbitmq-server' isn't showing you extra
> information is probably because you don't have other applications
> running colocated with rabbitmq-server.
>
> Looking at the initial output, all of those units were on machines
> 0,1,2,3,4.
>
> The other thing to consider is applications deployed into containers
> next to the applications that are on the host machine. I *think* we
> probably include those as well. (Certainly juju show-machine 0/juju
> status --format=yaml 0 show you the details of containers on that
> machine.)
>
> I haven't dug into each message in this thread to see if that is true.
>
> That said, I think a more expected output is that restricting by
> application might show you the machine that the unit is running on, but
> would filter out any other applications running on that machine.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1661407).
> https://bugs.launchpad.net/bugs/1592872
>
> Title:
>   juju status not showing correct output when specifying a specific
>   service/application
>
> Status in juju:
>   Triaged
>
> Bug description:
>   juju 2.0 beta8
>
>   When running juju status against a specific service/application (nova-
>   compute for example) the output of the command is very inconsistent.
>
>   Here are some examples:
>
>   ubuntu@maas:~$ juju status nova-compute
>   [Services]
>   NAME         STATUS  EXPOSED CHARM
>   ceph-osd     blocked false   cs:xenial/ceph-osd-2
>   nova-compute blocked false   cs:xenial/nova-compute-1
>
>   [Relations]
>   SERVICE1     SERVICE2     RELATION     TYPE
>   nova-compute nova-compute compute-peer peer
>
>   [Units]
>   ID             WORKLOAD-STATUS JUJU-STATUS VERSION   MACHINE PORTS
> PUBLIC-ADDRESS MESSAGE
>   ceph-osd/0     blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relation: monitor
>   ceph-osd/1     blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relation: monitor
>   ceph-osd/2     blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relation: monitor
>   ceph-osd/3     blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relation: monitor
>   ceph-osd/4     blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relation: monitor
>   nova-compute/0 blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relations: messaging, image
>   nova-compute/1 blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relations: messaging, image
>   nova-compute/2 blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relations: messaging, image
>   nova-compute/3 blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relations: messaging, image
>   nova-compute/4 blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relations: messaging, image
>
>   [Machines]
>   ID         STATE   DNS            INS-ID SERIES AZ
>   0          started 192.168.100.12 4y3h7q xenial default
>   1          started 192.168.100.13 4y3h7r xenial default
>   2          started 192.168.100.14 4y3h7s xenial default
>   3          started 192.168.100.15 4y3h7t xenial default
>   4          started 192.168.100.11 4y3h7p xenial default
>
>   ubuntu@maas:~$ juju status nova-compute
>   [Services]
>   NAME            STATUS  EXPOSED CHARM
>   ceph-osd        blocked false   cs:xenial/ceph-osd-2
>   neutron-api     blocked false   cs:xenial/neutron-api-1
>   neutron-gateway blocked false   cs:xenial/neutron-gateway-1
>   nova-compute    blocked false   cs:xenial/nova-compute-1
>   swift-storage   blocked false   cs:xenial/swift-storage-2
>
>   [Relations]
>   SERVICE1        SERVICE2        RELATION     TYPE
>   neutron-api     neutron-api     cluster      peer
>   neutron-gateway neutron-gateway cluster      peer
>   nova-compute    nova-compute    compute-peer peer
>
>   [Units]
>   ID                WORKLOAD-STATUS JUJU-STATUS VERSION   MACHINE PORTS
> PUBLIC-ADDRESS MESSAGE
>   ceph-osd/0        blocked         idle        2.0-beta8 0
> 192.168.100.12 Missing relation: monitor
>   ceph-osd/1        blocked         idle        2.0-beta8 1
> 192.168.100.13 Missing relation: monitor
>   ceph-osd/2        blocked         idle        2.0-beta8 2
> 192.168.100.14 Missing relation: monitor
>   ceph-osd/3        blocked         idle        2.0-beta8 3
> 192.168.100.15 Missing relation: monitor
>   ceph-osd/4        blocked         idle        2.0-beta8 4
> 192.168.100.11 Missing relation: monitor
>   neutron-api/0     blocked         idle        2.0-beta8 0       9696/tcp
> 192.168.100.12 Missing relations: messaging, identity, database
>   neutron-gateway/0 blocked         idle        2.0-beta8 0
> 192.168.100.12 Missing relations: messaging
>   nova-compute/0    blocked         idle        2.0-beta8 0
> 192.168.100.12 Missing relations: messaging, image
>   nova-compute/1    blocked         idle        2.0-beta8 1
> 192.168.100.13 Missing relations: messaging, image
>   nova-compute/2    blocked         idle        2.0-beta8 2
> 192.168.100.14 Missing relations: messaging, image
>   nova-compute/3    blocked         idle        2.0-beta8 3
> 192.168.100.15 Missing relations: messaging, image
>   nova-compute/4    blocked         idle        2.0-beta8 4
> 192.168.100.11 Missing relations: messaging, image
>   swift-storage/0   blocked         idle        2.0-beta8 0
> 192.168.100.12 Missing relations: proxy
>   swift-storage/1   blocked         idle        2.0-beta8 1
> 192.168.100.13 Missing relations: proxy
>   swift-storage/2   blocked         idle        2.0-beta8 2
> 192.168.100.14 Missing relations: proxy
>   swift-storage/3   blocked         idle        2.0-beta8 3
> 192.168.100.15 Missing relations: proxy
>   swift-storage/4   blocked         idle        2.0-beta8 4
> 192.168.100.11 Missing relations: proxy
>
>   [Machines]
>   ID         STATE   DNS            INS-ID SERIES AZ
>   0          started 192.168.100.12 4y3h7q xenial default
>   1          started 192.168.100.13 4y3h7r xenial default
>   2          started 192.168.100.14 4y3h7s xenial default
>   3          started 192.168.100.15 4y3h7t xenial default
>   4          started 192.168.100.11 4y3h7p xenial default
>
>   ubuntu@maas:~$ juju status nova-compute
>   [Services]
>   NAME            STATUS  EXPOSED CHARM
>   ceph-osd        blocked false   cs:xenial/ceph-osd-2
>   neutron-gateway blocked false   cs:xenial/neutron-gateway-1
>   nova-compute    blocked false   cs:xenial/nova-compute-1
>   swift-storage   blocked false   cs:xenial/swift-storage-2
>
>   [Relations]
>   SERVICE1        SERVICE2        RELATION     TYPE
>   neutron-gateway neutron-gateway cluster      peer
>   nova-compute    nova-compute    compute-peer peer
>
>   [Units]
>   ID                WORKLOAD-STATUS JUJU-STATUS VERSION   MACHINE PORTS
> PUBLIC-ADDRESS MESSAGE
>   ceph-osd/0        blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relation: monitor
>   ceph-osd/1        blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relation: monitor
>   ceph-osd/2        blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relation: monitor
>   ceph-osd/3        blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relation: monitor
>   ceph-osd/4        blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relation: monitor
>   neutron-gateway/0 blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relations: messaging
>   nova-compute/0    blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relations: messaging, image
>   nova-compute/1    blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relations: messaging, image
>   nova-compute/2    blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relations: messaging, image
>   nova-compute/3    blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relations: messaging, image
>   nova-compute/4    blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relations: messaging, image
>   swift-storage/0   blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relations: proxy
>   swift-storage/1   blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relations: proxy
>   swift-storage/2   blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relations: proxy
>   swift-storage/3   blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relations: proxy
>   swift-storage/4   blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relations: proxy
>
>   [Machines]
>   ID         STATE   DNS            INS-ID SERIES AZ
>   0          started 192.168.100.12 4y3h7q xenial default
>   1          started 192.168.100.13 4y3h7r xenial default
>   2          started 192.168.100.14 4y3h7s xenial default
>   3          started 192.168.100.15 4y3h7t xenial default
>   4          started 192.168.100.11 4y3h7p xenial default
>
>
>   expected output would be:
>
>   ubuntu@maas:~$ juju status nova-compute
>   [Services]
>   NAME         STATUS  EXPOSED CHARM
>   nova-compute blocked false   cs:xenial/nova-compute-1
>
>   [Relations]
>   SERVICE1     SERVICE2     RELATION     TYPE
>   nova-compute nova-compute compute-peer peer
>
>   [Units]
>   ID             WORKLOAD-STATUS JUJU-STATUS VERSION   MACHINE PORTS
> PUBLIC-ADDRESS MESSAGE
>
>   nova-compute/0 blocked         idle        2.0-beta8 0
>  192.168.100.12 Missing relations: messaging, image
>   nova-compute/1 blocked         idle        2.0-beta8 1
>  192.168.100.13 Missing relations: messaging, image
>   nova-compute/2 blocked         idle        2.0-beta8 2
>  192.168.100.14 Missing relations: messaging, image
>   nova-compute/3 blocked         idle        2.0-beta8 3
>  192.168.100.15 Missing relations: messaging, image
>   nova-compute/4 blocked         idle        2.0-beta8 4
>  192.168.100.11 Missing relations: messaging, image
>
>   [Machines]
>   ID         STATE   DNS            INS-ID SERIES AZ
>   0          started 192.168.100.12 4y3h7q xenial default
>   1          started 192.168.100.13 4y3h7r xenial default
>   2          started 192.168.100.14 4y3h7s xenial default
>   3          started 192.168.100.15 4y3h7t xenial default
>   4          started 192.168.100.11 4y3h7p xenial default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1592872/+subscriptions
>