Juju status reporting waiting apps incorrectly

Bug #1784672 reported by Charles Dunbar
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

On juju 2.4.1-xenial-amd64, I'm able to see odd output when performing a `juju status $APPNAME` that seems to have incorrect and unrelated information:

https://pastebin.ubuntu.com/p/8kVryqc8rP/

For some reason, ceph-osd is waiting wth a scale of 0, when running a `juju status neutron-gateway`

Looking into `juju status ceph-osd` - there's more waiting apps, and then with multiple runs you get different Units reported.

What might cause juju to have:
1) Incorrect status of apps in the status
2) Extra apps that aren't subordinates listed
3) With the ceph-osd status, the Unit table is different on the second run as well, with the same Apps as the first and third.

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

Please also paste the output of 'juju status --relations'. It seems that the additional apps are present in the output as there are relations linking them to the apps you've requested.

If this is the case, it has been done by design. If it is not the case, it's a bug and we need to figure out why additional, seemingly unrelated, apps are being listed.

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

The other reason for listing seemingly unrelated apps is when they have units on the same machines as the units of the apps that you are interested in.

Revision history for this message
Charles Dunbar (ccdunbar) wrote :

https://pastebin.ubuntu.com/p/tf6ZhWDBnW/ is the output of `juju status --relations`

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

@Charles Dunbar (ccdunbar),

Thank you for providing additional information.

The extra applications and their units that you've observed are listed because they either have a relation to the application you are filtering on OR they have units that reside on the same machines that the units of your application of interest.

However, I would have expected a consistent output on a stable system :) So, there is definitively an illusive bug somewhere. If you have an easier reproduction steps than me replicating your setup, it would be greatly appreciated \o/

Changed in juju:
status: Incomplete → Triaged
importance: Undecided → Medium
assignee: nobody → Anastasia (anastasia-macmood)
tags: added: status usability
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Charles Dunbar (ccdunbar),

There have been a few changes in status area including better filtering of relations and apps. Also the application filtering logic changed - previously we were pulling a lot based on the units & relations and machine sharing...

Could you please verify that 2.5-b3 works for you?
Alternatively, if you could help me to identify an easily reproducible, minimal scenario, I could verify the changes myself.

Changed in juju:
status: Triaged → Incomplete
Changed in juju:
assignee: Anastasia (anastasia-macmood) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
Revision history for this message
Junien F (axino) wrote :

This is still a problem with 2.5.0

Changed in juju:
status: Expired → Triaged
Changed in juju:
milestone: none → 2.6-beta1
Changed in juju:
milestone: 2.6-beta1 → 2.6-beta2
Changed in juju:
milestone: 2.6-beta2 → 2.6-rc1
Changed in juju:
milestone: 2.6-rc1 → 2.6-rc2
Changed in juju:
milestone: 2.6-rc2 → 2.6.1
Changed in juju:
milestone: 2.6.1 → 2.6.2
Changed in juju:
milestone: 2.6.2 → 2.6.3
Changed in juju:
milestone: 2.6.3 → 2.6.4
Changed in juju:
milestone: 2.6.4 → 2.6.5
Changed in juju:
milestone: 2.6.5 → 2.6.6
Changed in juju:
milestone: 2.6.6 → 2.6.7
Changed in juju:
milestone: 2.6.7 → 2.7-beta1
Changed in juju:
milestone: 2.7-beta1 → 2.7-rc1
Changed in juju:
milestone: 2.7-rc1 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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

Changed in juju:
importance: Medium → Low
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.