Skip to content
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

connection_retries doesn't seem to work? #200

Closed
empath opened this issue Oct 20, 2015 · 2 comments
Closed

connection_retries doesn't seem to work? #200

empath opened this issue Oct 20, 2015 · 2 comments

Comments

@empath
Copy link

empath commented Oct 20, 2015

I may misunderstand what it does, but I have this in my .kitchen.yml file.

transport:
ssh_key: ~/key
username: ec2-user
connection_retries: 20

I had an AMI that would boot, but SSH would never start working, and it just continuously printed Waiting for SSH service on 10.97.19.32:22, retrying in 3 seconds
Waiting for SSH service on 10.97.19.32:22, retrying in 3 seconds

for several hundred lines before I noticed. Am I missing something obvious here? Should it not have just tried 20 times and then failed? Is there some other way to time out a kitchen test if ssh doesn't start working?

@JaBurd
Copy link

JaBurd commented Oct 21, 2015

I've also tried to modify the max_wait_until_ready attribute. That also doesn't seem to have an impact. If the node doesn't spin up in < 300s it will auto terminate. None of the settings I've attempted to modify seem to have any impact.

@cheeseplus
Copy link
Contributor

See this post, that should address the issued and if not feel free to open a new issue #103 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants