Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
api/controller: allow empty CACert in migration #7315
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
$$merge$$ |
|
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 633d641
into
juju:develop
May 11, 2017
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rogpeppe commentedMay 8, 2017
This allows a model to be migrated to a controller with a
global CA certificate, the common case when using the
JIMM controller.
QA add a controller with an autocert-dns-name configuration,
configure the appropriate DNS entry to point to the controller
instance, remove the ca-cert entry from its controllers.yaml entry,
and try to migrate a model from another controller to that one.