Ensure that the call to Net::SSH.start only uses the key provided in the manifest, by feeding it the keys_only: true parameter.

[jrbudnack]

I ran into a little-known issue when trying to deploy a MicroBOSH. After deploying to my OpenStack, the bosh micro plugin was trying to ssh into my new instance, but was unsuccessful. The stemcell used was bosh-stemcell-2889-openstack-kvm-ubuntu-trusty-go_agent, deploying to Openstack Havana.

The problem turned out to be that I have more than 5 keys in my ~/.ssh directory. The instance in question only allowed 5 attempts before refusing the ssh connection. The way Ruby's Net::SSH.start works, is it tries the keys in your ~/.ssh directory AND the keys you provide as a parameter to it. So, what was happening is 5 of my own keys were used first in trying to connect. When they failed, the key in the manifest was never actually tried. Next attempt would start... and the cycle would continue.

To limit Net::SSH.start to just using the key provided as a parameter (i.e.: the key provided in the MicroBOSH manifest) is to add the following parameter:

keys_only: true

This solved my issue.

[cfdreddbot]

Hey jrbudnack!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

[jrbudnack]

bump @cppforlife ^^

[cppforlife]

@jrbudnack since we are trying to avoid making more changes to micro CLI plugin since we are pushing people to use bosh-init. Also I'm not sure if some people may depend on this behavior already. Have you tried bosh-init?

[cppforlife]

Closing as per last comment.