Juju wait doesn't recognize restarted machines

Bug #1989735 reported by Bas de Bruijne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Undecided
Unassigned
Juju Wait Plugin
New
Undecided
Unassigned

Bug Description

In testrun https://solutions.qa.canonical.com/testruns/testRun/a316d533-e206-4c2f-aad4-05646418afbb, the following happens:

1) machine 6 goes down for one reason or another
2) machine 6 comes back up
3) juju recognizes it and changes the machine status from `lost` to `started`
4) juju wait fails with the message `ERROR:root:Machine 6 is in down for 31 minutes.`

This message is true in the sense that it was 31 minutes ago that the machine went down but since the machine has come back up within 31 min it should not be a blocking error for juju wait.

Crashdumps for this run can be found here:
https://oil-jenkins.canonical.com/artifacts/a316d533-e206-4c2f-aad4-05646418afbb/index.html

tags: added: cdo-qa foundations-engine
Changed in juju:
status: New → Incomplete
status: Incomplete → Invalid
Revision history for this message
Vitaly Antonenko (anvial) wrote :

Maybe it will be helpful to have a look at: https://juju.is/docs/olm/juju-wait-for

Revision history for this message
Joseph Phillips (manadart) wrote :

The juju-wait plugin is not owned by the Juju team.

Consider using the wait-for plugin. This is a Juju-developed plugin on the 2.9 version, which has been made native in Juju 3+.

https://discourse.charmhub.io/t/juju-wait-for/3695

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.