-
Notifications
You must be signed in to change notification settings - Fork 9k
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 waiting for KMS Key tag propagation: timeout while waiting for state to become 'TRUE' -- KMS tag bug #26174
Comments
Is there any update on this one? Our teams run into this on almost a daily basis and it feels like it is starting to happen more due to the number of reports we are seeing. It would be great if the limit was increased again or if the underlying problem was resolved. Currently teams have their pipelines fail regularly due to this and then need to run a fresh pipeline and new TF Apply that then passes. |
It waited 10 minutes, timed out ran it again and it didn't even try and change the tags. So it's like it's doing it but doesn't realize it. |
+1 due to running into the same problem. |
This functionality has been released in v5.14.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform Version: v0.13.4
Terraform AWS Provider version: 4.9.0
Affected Resource(s)
Terraform Configuration Files
Debug Output
Gist here
Expected Behavior
Terraform updates the KMS key's tags without producing a timeout error
Actual Behavior
Terraform times out after 10 minutes
Steps to Reproduce
terraform apply
References
Related to issue #23592 where the solution back then was to increase the timeout from 5m to 10m
Note: a location in S3 is the backend used for the statefile
The text was updated successfully, but these errors were encountered: