-
Notifications
You must be signed in to change notification settings - Fork 660
spot-instances-request tags breaks on-demand instances #4561
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
Comments
Thx for reporting, If time allows would you be great if you can raise a PR.
|
Created a PR, rquires some testing before merging. |
Fix available in release https://github.com/github-aws-runners/terraform-aws-github-runner/releases/tag/v6.5.4 should be available |
Hi @npalm, thanks for the help. Thank you for the help and the rapid fix! |
Hi, I still have this issue when spot instances are not available and trying to fallback on on-demand My logs are :
Thanks for your help |
Hi.
Today we upgraded the module from version 6.4.3 to 6.5.1. Our groups based only on on-demand instances got stuck right after the upgrade. The scale-up lambda silently fails with this error:
"You cannot specify tags for Spot instances requests if there are no Spot instances requests being created by the request."
Below you can see the whole lambda logs:
logs.txt
How can we avoid putting those tags in the launch template when running only on-demand instances?
Thanks!
The text was updated successfully, but these errors were encountered: