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/uniter: handle conflicted upgrades #3121
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
axw
added some commits
Aug 27, 2015
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
added a commit
that referenced
this pull request
Aug 27, 2015
jujubot
merged commit ed44bb5
into
juju:maltese-falcon
Aug 27, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
axw commentedAug 27, 2015
This PR fixes conflicted upgrade handling. If an
upgrade fails due to a conflict, we now set the
LocalState's Conflicted field to true, and then
we clear it when an upgrade operation is committed.
When in the conflicted state, we only accept two
methods of progressing: hook resolution, or a
forced upgrade. One creates a resolved-upgrade op,
and the other creates a revert-upgrade op. If
neither of these is true, we'll just for a state
change.
We also simplify handling of the Stopped local
state. If the unit has already run the Stop hook,
then it should not generate any more operations.
So we now check for life==Dead or Stopped at the
top of NextOp.
(Review request: http://reviews.vapour.ws/r/2500/)