can wait forever when one or more units fail during deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Invalid
|
Undecided
|
Unassigned | ||
juju-deployer |
Invalid
|
Undecided
|
Tim Van Steenburgh | ||
python-jujuclient |
New
|
Undecided
|
Tim Van Steenburgh |
Bug Description
When a unit hangs/fails during deployment, mojo (and juju-deployer) deployments can infinitely wait for deploy completion. The expected behavior, regardless of the health of the deployed units, would be for it raise and exit when the timeout threshold is hit.
This is occurring when one or more units in the deployment have crashed or hung during hook execution (that is an unrelated separate issue, such as a hung_task).
jenkins@
juju-core:
Installed: 1.25.0-
Candidate: 1.25.0-
Version table:
*** 1.25.0-
500 http://
100 /var/lib/
1.
500 http://
1.
500 http://
jenkins@
juju-deployer:
Installed: 0.6.0-1
Candidate: 0.6.0-1
Version table:
*** 0.6.0-1 0
500 http://
100 /var/lib/
0.3.6-0ubuntu2 0
500 http://
jenkins@
mojo:
Installed: 0.1.15
Candidate: 0.1.15
Version table:
*** 0.1.15 0
500 http://
100 /var/lib/
# mojo/deployer output:
http://
# juju stat
http://
Related branches
- Ryan Beisner (community): Approve
- juju-deployers: Pending requested
-
Diff: 39 lines (+15/-2)1 file modifiedjujuclient.py (+15/-2)
Changed in juju-deployer: | |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
Changed in python-jujuclient: | |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
Changed in juju-deployer: | |
status: | New → Invalid |
Changed in mojo: | |
status: | New → Invalid |
Added juju-deployer as we did observe the same with vanilla (non-mojo) juju-deployer test runs.
ex.
Stuck for over a day, juju-deployer never timed out:
http:// paste.ubuntu. com/13086320/