Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
state: Squash another unknown collection error #7385
+12
−0
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 |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit 5291b1e
into
juju:develop
May 25, 2017
1 check passed
github-check-merge-juju
Built PR, ran unit tests, and tested LXD deploy. Use !!.*!! to request another build. IE, !!build!!, !!retry!!
Details
babbageclunk
deleted the
babbageclunk:unknown-collection
branch
May 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
babbageclunk commentedMay 24, 2017
•
Edited 1 time
-
babbageclunk
May 25, 2017
Description of change
We were seeing another
unknown collection "remoteApplications"error which turned out to be from Relation.IsCrossModel - it needed to check the feature flag.Dump stack when an unknown collection is requested and we're in developer mode. This will make it much easier to find them in future.
QA steps
Create a model, deploy mysql and wordpress to it, relate them together, destroy the model. The unknown collection error shouldn't appear in the logs.