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/migrationmaster: ABORT failure not status #6718
Conversation
| -// Activate sets the migration mode of the model to "active". It is an error to | ||
| -// attempt to Abort a model that has a migration mode other than importing. | ||
| +// Activate sets the migration mode of the model to "none", meaning it | ||
| +// is ready for us. It is an error to attempt to Abort a model that |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit b16bafe
into
juju:2.1
Dec 15, 2016
1 check failed
github-check-merge-juju
Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details
mjs
referenced this pull request
Jan 9, 2017
Merged
worker/migrationmaster: ABORT failure not status #6785
added a commit
that referenced
this pull request
Jan 9, 2017
mjs
deleted the
mjs:MM-tweaks
branch
Feb 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mjs commentedDec 15, 2016
A failure to remove the model from the target controller during ABORT is often completely normal (i.e. the migration never got to importing it). Don't record this failure to a migration status update as it obscures the real reason for the abort.
Drive-by: Correct docstring for MigrationTarget.Activate.
No QA necessary.