Juju Wait Plugin

juju-check-wait waits for subordinate charms with no relations

Bug #1629409 reported by Tim Kuhlman
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Juju Wait Plugin
Incomplete
High
Unassigned
Mojo: Continuous Delivery for Juju
Triaged
Medium
Unassigned

Bug Description

In some cases subordinate charms are added with no corresponding relations, this puts them into a waiting state but no one that juju-check-wait should hang for.

The difficulty is that from the status output it isn't clear that it is a subordinate with no relations.

 ksplice:
    charm: local:xenial/ksplice-3
    series: xenial
    os: ubuntu
    charm-origin: local
    charm-name: ksplice
    charm-rev: 3
    exposed: false
    application-status:
      current: waiting
      message: waiting for machine
      since: 30 Sep 2016 17:03:45Z

Revision history for this message
Tom Haddon (mthaddon) wrote :

I've added Stuart as a subscriber. Stuart, is this a change in juju 2 output that's making it harder to tell whether it's a subordinate? Just wondering how this was handled in a juju 1 world. Potentially we should file a bug against juju asking for a change to the status output to make it obvious that something is a subordinate.

Revision history for this message
Stuart Bishop (stub) wrote :

This is just an edge case I didn't think of. Any service/application deployed to 0 units should not be blocking anything.

Changed in mojo:
status: New → Triaged
Changed in juju-wait:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Stuart Bishop (stub) wrote :

I can't reproduce this with juju-wait(1). Any application/service with no units is ignored completely, as all the checks are done by iterating over units. The place it might have been a problem (the leadership check) avoided the issue, possibly by accident.

Changed in juju-wait:
status: Triaged → Incomplete
Revision history for this message
Stuart Bishop (stub) wrote :

https://code.launchpad.net/~stub/mojo/devel/+merge/307426 , but I don't think it will help. I think something else went wrong, perhaps a hook loop. If the verbose wait output is enabled somehow it might give more information.

Tom Haddon (mthaddon)
Changed in mojo:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.