Rescue Errno::ETIMEDOUT instead of Timeout::Error on Establish

[Annih]

Fix #800
net-ssh 2.10 does not use 'timeout' anymore, it use the Socket connect_timeout instead.
See: net-ssh/net-ssh@58b3797 and net-ssh/net-ssh@9bfbdc9

[tyler-ball]

@Annih will you rebase this off master? Should fix the appveyor issue

[tyler-ball]

Hey @Annih I took care of the merge. I changed the code to catch both errors and retry them so it works with net-ssh 2.9 and 2.10

Also, thanks for this PR and getting the ball rolling on these fixes!

[Annih]

Sorry for the delay @tyler-ball and thanks for the quick release!

[komuta]

@tyler-ball I think the problem is still there, at least when using net-ssh 2.10, because Timeout::Error is still referenced in the code but not in net-ssh anymore :

-----> Starting Kitchen (v1.4.2)
------Exception-------
Class: Kitchen::ClientError
Message: Could not load the 'ssh' transport from the load path. Please ensure that your transport is installed as a gem or included in your Gemfile if using Bundler.
---Nested Exception---
Class: NameError
Message: uninitialized constant Kitchen::Transport::Ssh::Connection::Timeout

Tested with ruby 2.1.2, Kitchen 1.4.2, net-ssh 2.10.0beta2

[tyler-ball]

@komuta Thanks for the report! What does your environment look like? Are you using the ChefDK?

Can you modify lib/kitchen/transport/ssh.rb locally and add a require 'timeout' at the top? I'm guessing that will fix the NameError you are seeing. If it does, would you mind submitting a PR and pinging me?

[komuta]

I was just beginning to try Test Kitchen with Vagrant, Ansible and Serverspec. I don't use Chef at all.

I did the modification and now it works perfectly well. I'll submit a new pull request.

[komuta]

@tyler-ball Here is the PR : #866