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

Instace type m5.large / New regions are not working #473

Closed
avishayil opened this issue Nov 19, 2019 · 4 comments
Closed

Instace type m5.large / New regions are not working #473

avishayil opened this issue Nov 19, 2019 · 4 comments

Comments

@avishayil
Copy link

avishayil commented Nov 19, 2019

When trying to provision instances with the m5.large type, kitchen cannot connect to those instances and therefore kitchen create fails. When I change the parameter to m4.large it works, not sure what could be the reason. Tested on several regions.

Edit: Appears that several instance types from the 5 family are not working, such as c5.2xlarge

Edit: Appears that on AWS new regions (eu-north-1), several instance types are not working, such as t3, m5, c5

@avishayil
Copy link
Author

Even though create fails, if I stop create forcefully and wait for some time, I can converge the instance successfully.

Any idea how to solve the create issue?

@avishayil avishayil changed the title Instace type m5.large is not working Instace type m5.large / New regions are not working Nov 19, 2019
@avishayil
Copy link
Author

It takes double time on these regions

@rwc
Copy link

rwc commented Mar 23, 2020

@avishayil - Did you have to increase your timeouts for kitchen in order for it to connect? If so, what value did you change it to?

@avishayil
Copy link
Author

Hi @rwc , 600 seconds.

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

2 participants