Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
migrations: Import principal applications first #6731
Conversation
|
Huh, that's irritating - I can never get it to fail like that locally. Ok, I'll change the test to marshal the model, reorder those elements and unmarshal. |
|
Came up with a nicer way to swap them. !!chittychitty!! |
| @@ -389,6 +389,71 @@ func (s *MigrationImportSuite) TestApplicationLeaders(c *gc.C) { | ||
| }) | ||
| } | ||
| +func (s *MigrationImportSuite) TestApplications_SubordinatesAfter(c *gc.C) { |
babbageclunk
Dec 19, 2016
Member
Sure - although I think Katherine is advocating in the other direction.
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit 2e110f2
into
juju:develop
Dec 19, 2016
babbageclunk
deleted the
babbageclunk:mm-subordinate-charms
branch
Dec 19, 2016
babbageclunk
referenced this pull request
Dec 19, 2016
Merged
migrations: Import principal applications first (backport) #6734
added a commit
that referenced
this pull request
Dec 19, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
babbageclunk commentedDec 19, 2016
•
Edited 1 time
-
babbageclunk
Dec 19, 2016
Otherwise the import fails because the subordinate units refer to
nonexistent principal units.
Fixes https://bugs.launchpad.net/juju/+bug/1650249
QA steps:
juju dump-model.