Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
provider/gce: don't set sshKeys instance metadata #6294
Conversation
|
QA
|
hatched
referenced this pull request
in juju/juju-gui
Sep 21, 2016
Closed
Unable to deploy to new models on GCE #2027
reedobrien
approved these changes
Sep 21, 2016
LGTM, but IANAGR.
Fixing a but purely by removing code. Awesome.
QA Checks out.
anastasiamac
approved these changes
Sep 21, 2016
Love it! Thanks \o/
I think it'll also help with this experience https://bugs.launchpad.net/juju/+bug/1624548
|
$$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 1a2e3ba
into
juju:master
Sep 22, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
axw commentedSep 21, 2016
The GCE provider is bailing from StartInstances if
authorized-keys is empty. It should not be doing
this.
Also, we're only looking at authorized-keys in the
GCE provider to set the sshKeys instance metadata.
This is what GCE uses to keep track of the SSH keys
that it manages on an instance. We should not be
setting this; using cloud-init is sufficient.
Fixes https://bugs.launchpad.net/bugs/1625881