Kitchen setup on Centos6.4 fails initial ssh auth with valid credentials

[gmiranda23]

While validating that #85 is resolved, I ran into this new (related?) issue with ssh on Centos6.4 with kitchen-ec2. Valid login credentials are supplied but initial SSH connection fails. Credentials verified by attempting login from a different session. With kitchen, the initial SSH attempt bombs out (key auth fails and I simply enter nothing for password 3 times), SSH retries the connection and this time it works.

$ kitchen setup
-----> Starting Kitchen (v1.4.0)
-----> Creating <default-centos-64>...
       Creating <>...
If you are not using an account that qualifies under the AWS
free-tier, you may be charged to run these suites. The charge
should be minimal, but neither Test Kitchen nor its maintainers
are responsible for your incurred costs.

       Instance <i-fb72eb0c> requested.
       EC2 instance <i-fb72eb0c> created.
       Waited 0/300s for instance <i-fb72eb0c> to become ready.
       Waited 5/300s for instance <i-fb72eb0c> to become ready.
       Waited 10/300s for instance <i-fb72eb0c> to become ready.
       Waited 15/300s for instance <i-fb72eb0c> to become ready.
       Waited 20/300s for instance <i-fb72eb0c> to become ready.
       EC2 instance <i-fb72eb0c> ready.
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
    root@ec2-52-25-141-157.us-west-2.compute.amazonaws.com's password:
    root@ec2-52-25-141-157.us-west-2.compute.amazonaws.com's password:
    root@ec2-52-25-141-157.us-west-2.compute.amazonaws.com's password:
       Waiting for SSH service on ec2-52-25-141-157.us-west-2.compute.amazonaws.com:22, retrying in 3 seconds
       [SSH] Established
       Finished creating <default-centos-64> (2m20.17s).
       ...

$ chef -v
Chef Development Kit Version: 0.6.0
chef-client version: 12.3.0
berks version: 3.2.4
kitchen version: 1.4.0

$ chef gem list kitchen-ec2
*** LOCAL GEMS ***
kitchen-ec2 (0.9.2)

Relevant bits of .kitchen.yml
driver:
  name: ec2
  aws_ssh_key_id: my-ssh-key
  region: us-west-2
  require_chef_omnibus: true
  instance_type: m3.medium
  security_group_ids: [ "default" ]

transport:
  ssh_key: /Users/gmiranda/.ssh/my-ssh-key
  username: root

[tyler-ball]

Hey @gmiranda23 - thanks for the bug report. I think we have a fix for this merged into TK master - can you try using the latest master branch locally via my instructions from #129 (comment) and let us know if that fixes your issue?

[gmiranda23]

That fixed it. Looking forward to the release!