Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
worker/provisioner: Increase start instance retry limit #7351
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit 0be1f59
into
juju:develop
May 16, 2017
1 check passed
github-check-merge-juju
Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details
babbageclunk
deleted the
babbageclunk:maas-bug
branch
May 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
babbageclunk commentedMay 16, 2017
Description of change
QA are seeing a MAAS deployment timeout occasionally, it looks like it's
caused by the retry limit in the provisioner - in some cases MAAS is
busy enough that 3 failures might happen while trying to start an
instance.
Bump up the retry limit to 10 as a simple fix for the immediate problem
separate change).
QA steps
Deploying still works on MAAS.
It's hard to reproduce this problem on my own MAAS.
Bug reference
Fixes https://bugs.launchpad.net/juju/+bug/1688028