Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Store separate migration attempt number #6715
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
mjs
closed this
Dec 15, 2016
mjs
deleted the
mjs:MM-migration-sorting
branch
Dec 15, 2016
mjs
restored the
mjs:MM-migration-sorting
branch
Dec 15, 2016
mjs
reopened this
Dec 15, 2016
|
Build failed: Tests failed |
mjs
added some commits
Dec 15, 2016
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit 6d421fb
into
juju:2.1
Dec 19, 2016
mjs
deleted the
mjs:MM-migration-sorting
branch
Jan 7, 2017
added a commit
that referenced
this pull request
Jan 7, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mjs commentedDec 15, 2016
•
Edited 1 time
-
mjs
Dec 15, 2016
In order to allow correct sorting of migration documents when there's been 10 or more attempts (note: 2 digits), the attempt number is now stored in a separate document field. This also simplifies the Attempt()
API, negating the need for an error return.
Upgrade step for preexisting migration documents included.
QA
Ran a migration and confirmed by DB inspection that an attempt field was on the migration document. Then manually removed the field, modified the upgradedToVersion in the controller's agent.conf and restarted the controller agent to trigger upgrade steps to run. Inspecting the DB again showed that the correct attempt field had been added.