-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Error launching new instance after release 19.2.0 #2361
Comments
Same issue here. All our EC2 nodes were destroyed & all pods are now stuck Pending. |
This issue has been resolved in version 19.4.0 🎉 |
@bryantbiggs as mentioned in the PR spot request should be removed from the default list as well! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
When release 19.2.0 was created
tag_specifications
were introduced, which are being applied to a bigger set of tags. This is causing our launch templates not being able to schedule a new instance, because we do not deploy any Elastic GPUs.Versions
Module version [Required]:
19.3.1
Terraform version:
1.3.4
Provider version(s):
1.3.4
The text was updated successfully, but these errors were encountered: