Merge lp:~aisrael/juju-deployer/workaround-lp-1421315 into lp:juju-deployer
Proposed by
Adam Israel
Status: | Merged |
---|---|
Merged at revision: | 146 |
Proposed branch: | lp:~aisrael/juju-deployer/workaround-lp-1421315 |
Merge into: | lp:juju-deployer |
Diff against target: |
63 lines (+25/-6) 1 file modified
deployer/action/importer.py (+25/-6) |
To merge this branch: | bzr merge lp:~aisrael/juju-deployer/workaround-lp-1421315 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tim Van Steenburgh (community) | Approve | ||
Review via email: mp+254328@code.launchpad.net |
Description of the change
I recently ran into a bug lp:1421315 while reviewing a merge request (lp:238283)
juju-deployer would throw an exception due to the service not being available in the watch status output. This fix expands on the original workaround, to wait 5.1 seconds for status (which is supposed to be available in 5 seconds) to be available. In this merge, the check is wrapped in a while block that will attempt to read the status for the specific unit, for up to 60 seconds, before failing.
I have tested this against the above merge request, and it eliminated all related testing errors.
To post a comment you must log in.
The merge that this was affecting is: https:/ /code.launchpad .net/~stub/ charms/ precise/ postgresql/ enable- integration- tests/+ merge/238283