-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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 tracking route_table_association on deletion #3615
Comments
We're running into the same problem every now and then and I'm looking forward to having this fixed in TF! |
Hey all – the supplied config file applied successfully for me (both creation and deletion). Is it sporadic? You mention race condition, do you have an idea of how often it happens? |
Yes it's definitely sporadic. I just checked my CI builds and I would say this happens about 20% of the time. |
provider/aws: ignore association not exist on route table destroy [GH-3615]
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. |
This happens from time to time on terraform destroy, I believe it to be caused by a race condition between route_table and route_table_association.
This looks very much like #2295, so I will propose a similar fix.
Version: terraform 0.6.3 linux x64
Initial terraform configuration
logs
The text was updated successfully, but these errors were encountered: