juju-wait should have a configurable timeout
Bug #1526307 reported by
Tom Haddon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Wait Plugin |
New
|
Undecided
|
Unassigned | ||
| Mojo: Continuous Delivery for Juju |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
We recently saw an instance where a subordinate was stuck in "Waiting for agent initialization to finish" for over 14 hours. We needed to restart jujud to allow it to continue. In the meantime juju-wait was simply continuing to wait. Juju-wait should have a configurable timeout so that this can be flagged as an error in CI runs, for instance, at an earlier point.
| Changed in mojo: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Tim Kuhlman (timkuhlman) wrote | #1 |
| Changed in mojo: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
I believe this has been fixed in the latest code juju-check-wait and the juju wait as part of juju deploy both have the 'status-timeout' option with a default value of 1800 seconds.