ssh_keys not working on droplet create

[shortdudey123]

I am trying to create a droplet, however, the ssh_keys array does not appear to get passed along during creation

[20] pry(main)> client.ssh_keys.find(id: 1234567)
=> <DropletKit::SSHKey {:@id=>1234567, :@fingerprint=>"XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX", :@public_key=>"ssh-rsa XXXXXXXXXXXX", :@name=>"ssh key name"}>
[21] pry(main)> droplet
=> <DropletKit::Droplet {:@name=>"new-droplet", :@size=>"2gb", :@image=>"centos-7-0-x64", :@region=>"nyc1", :@ssh_keys=>["1234567"], :@private_networking=>true, :@backups=>nil, :@ipv6=>nil, :@id=>nil, :@memory=>nil, :@vcpus=>nil, :@disk=>nil, :@locked=>nil, :@created_at=>nil, :@status=>nil, :@backup_ids=>nil, :@snapshot_ids=>nil, :@action_ids=>nil, :@features=>nil, :@networks=>nil, :@kernel=>nil, :@size_slug=>nil, :@user_data=>nil}>
[22] pry(main)> server = client.droplets.create(droplet)
=> <DropletKit::Droplet {:@name=>"new-droplet", :@size=>nil, :@image=><DropletKit::Image {:@id=>14782842, :@name=>"7.1 x64", :@distribution=>"CentOS", :@slug=>"centos-7-0-x64", :@public=>true, :@regions=>["nyc1", "sfo1", "nyc2", "ams2", "sgp1", "lon1", "nyc3", "ams3", "fra1", "tor1"], :@type=>"snapshot"}>, :@region=><DropletKit::Region {:@slug=>"nyc1", :@name=>"New York 1", :@sizes=>["512mb", "8gb", "16gb", "32gb", "48gb", "64gb", "1gb", "2gb", "4gb"], :@available=>true, :@features=>["private_networking", "backups", "ipv6", "metadata"]}>, :@ssh_keys=>nil, :@private_networking=>nil, :@backups=>nil, :@ipv6=>nil, :@id=>11162726, :@memory=>2048, :@vcpus=>2, :@disk=>40, :@locked=>true, :@created_at=>"2016-02-16T20:01:36Z", :@status=>"new", :@backup_ids=>[], :@snapshot_ids=>[], :@action_ids=>nil, :@features=>["virtio"], :@networks=>#<struct DropletKit::NetworkHash v4=[], v6=[]>, :@kernel=><DropletKit::Kernel {:@id=>6028, :@name=>"CentOS 7 x64 vmlinuz-3.10.0-229.20.1.el7.x86_64", :@version=>"3.10.0-229.20.1.el7.x86_64"}>, :@size_slug=>"2gb", :@user_data=>nil}>
[23] pry(main)> server.ssh_keys
=> nil
[24] pry(main)> 

[phillbaker]

Ah, @shortdudey123 thanks for opening an issue. We don't include the ssh keys that a droplet was created with in the response, which is why it returns nil. Since ssh keys can be modified on the host post creating a droplet, the keys that a droplet was created with may quickly/immediately be out of date.

However, the keys should have been used to actually create the droplet - with valid ids/keys does that call work?

[shortdudey123]

does that call work?

No, the ssh_keys array does not get passed onto the droplet for creation. I am unable to ssh to the new droplet. If i create one through the UI using the same ssh key it works.

[CloudCowboyCo]

Hey @shortdudey123,

This is what I use to pull my premade keys from DO.
https://gist.github.com/CloudCowboyCo/5eb34bec6ecc9a68f249
I couldn't tell if you were trying to hand off the key on creation.

If you are trying to add a key that you haven't added to DO previously you could accomplish this inside the userdata section of the droplet kit.

edit: put the wrong username :P

[shortdudey123]

@CloudCowboyCo the ssh key i am trying to pass in the array already exists on DO. That is verified with the first line of the output in my original post :)

[CloudCowboyCo]

Sorry, I saw the value as nil when returned. I should have read more closely. This is how I accomplish spinning up a droplet with my keys already on the system https://github.com/CloudCowboyCo/do-cocaine/blob/master/droplet_deploy.rb Let me know if this helps you out.

[shortdudey123]

Thanks, i am using the knife-digital_ocean gem to create the droplets (already ruled that out since i know that the ssh key is being passed to stuff in the droplet_kit gem)

[phillbaker]

@shortdudey123 our logs show that the API request was received with a ssh key and that the droplet was created with it.

It might help to open a ticket with some of the details (https://cloud.digitalocean.com/support/tickets/new) and we can help you debug further.

[shortdudey123]

Done, thanks

[jwadolowski]

Hey @shortdudey123 - did you find out what was the problem? Out of the blue I started to see exactly the same issues with kitchen-digitalocean (it uses droplet_kit under the hood).

[shortdudey123]

@jwadolowski nope, by the time digital ocean support got back to be I was unable to reproduce the issue

[phillbaker]

@jwadolowski what are the symptoms you're seeing? Don't believe this is a droplet kit specific issue: we've verified that DropletKit is passing the correct params and Droplets are being created with ssh keys.

Note that after a droplet (VM) is created, it may take some time for the OS and sshd to boot. If you wait for a bit and retry a connection to a droplet does that ever work?

[shortdudey123]

one thing i had thought about doing, but never did was to do a root password reset then use that to login through the web shell interface and see if the pub key is in the ~/.ssh/authorized_keys file

[jwadolowski]

@phillbaker actually symptoms are the same as originally reported by @shortdudey123 - SSH key is not passed through to my droplet.

It's definitely not the case related to boot time and sshd start as retry is already implemented in test-kitchen itself and it worked fine for months.

To narrow it down a little bit I wrote and executed this (it is essentially what happens in kitchen-digitalocean):

require 'droplet_kit'

client = DropletKit::Client.new(access_token: ENV['DIGITALOCEAN_ACCESS_TOKEN'])
client.ssh_keys.find(id: ENV['DIGITALOCEAN_SSH_KEY_IDS'])
droplet = DropletKit::Droplet.new(
    name: 'droplet-kit-test',
    image: 'centos-7-0-x64',
    size: '1gb',
    region: 'fra1',
    ssh_key_ids: ENV['DIGITALOCEAN_SSH_KEY_IDS'],
    private_networking: true, 
    ipv6: false
)
d = client.droplets.create(droplet)
d.ssh_keys

Last line returns nil.

Env variables:

DIGITALOCEAN_ACCESS_TOKEN=xxxxxx
DIGITALOCEAN_SSH_KEY_IDS=yyyyyy

[jwadolowski]

Good point @shortdudey123. I've just logged in and root's ~/.ssh/authorized_keys file is empty.

$ ssh root@46.101.X.X
root@46.101.X.X's password: 
You are required to change your password immediately (root enforced)
Last login: Mon Mar  7 19:38:59 2016 from X.Y.Z
Changing password for root.
(current) UNIX password: 
New password: 
Retype new password: 
[root@droplet-kit-test ~]# cat .ssh/authorized_keys 

[root@droplet-kit-test ~]#