-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kitchen attempts to log in before sshd is ready #85
Comments
Confirmed. I got around this by setting Perhaps this should be a setting managed in amis.json? |
I'm going to try and repro this so I can see where in the code it is failing - it may make sense to hardcode retry logic in there, or default the EDIT |
Hey @scarolan - can you try this again with the latest version of kitchen-ec2 (0.9.0) and see if this is still an issue? We updated to use the Test Kitchen 1.4 logic which greatly improved transport issues. |
I'm going to go ahead and close this since I haven't gotten a response - please re-open if you're still having problems with the latest version of kitchen-ec2! |
Could not verify due to #137 |
This is on the plain vanilla CentOS 6.5 AMI from the marketplace. Kitchen fails to log in the first time i run 'kitchen converge', then the second time I run it succeeds. I think it should wait maybe 5-10 seconds after port 22 is open to allow the machine to become fully ready.
The text was updated successfully, but these errors were encountered: