Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
migration: set model.Type now that 2.2 is exporting a v4 Model #7991
Conversation
babbageclunk
added some commits
Oct 30, 2017
|
$$merge$$ |
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
jujubot
merged commit 8a1aa58
into
juju:2.2
Oct 31, 2017
1 check passed
continuous-integration/jenkins/pr-merge
This commit looks good
Details
babbageclunk
deleted the
babbageclunk:set-model-type-2.2
branch
Oct 31, 2017
added a commit
to babbageclunk/juju
that referenced
this pull request
Oct 31, 2017
added a commit
that referenced
this pull request
Oct 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
babbageclunk commentedOct 31, 2017
Description of change
The description dependency was updated on the 2.2 branch (such that it
now exports v4 models). For correctness sake we should be setting the model type
(although I will also change the 2.3 branch to accept a blank model type so that migrating
from a 2.2.5 or .6 controller to a 2.3 one will work).
Includes a driveby to limit status history entries to 20 in exported models.
QA steps
Bootstrap a 2.3-beta1 controller (B) and a 2.2 branch one with this change in it (A).
Migrate a model from A to B. It should succeed, and there shouldn't be an error about
blank model types.
Bug reference
Part of the fix for https://bugs.launchpad.net/juju/+bug/1728486