-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/aws: IGW sometimes takes time to create #2174
Comments
That's frustrating 😢, specifically the non-trivial part which makes a minimal case hard to reproduce. Checking the API, I'm not sure what we can do. It sounds like an "eventual consistency inside AWS" type thing. The Is there a particular resource that's trying to use this IGW? Maybe we could poll a time or two if we get this error :/ |
I will try and see if I can debug it in any way and come up with any meaningful way of fixing it... |
I hope this wasn't received as push-back! It was intended as an expression of mutual suffering :) |
It was an expression of mutual suffering from my side as well. 😸 |
Just to add some details about this. The IGW was "detached" when that error occurred and remained so for a chunk of time. Then subsequent |
Hey @radeksimko – is there any thing you think we can do here, or can we close this in mutual suffering? 😄 |
I'm not sure it's worth playing the whack-a-mole here with resources since this behaviour will likely apply to other resources too... :/ I was thinking of adding something like this: resource.Retry(1*time.Minute, func() error { for the read API request. |
to the resourceAwsInternetGatewayCreate method? A |
Yeah, a We see this issue pretty frequently. |
I also encounter this issue sometimes. When I check the AWS console again, the internet Gateway is actually created. Below is the error message. InvalidInternetGatewayID.NotFound: The internetGateway ID 'igw-84cf01e1' does not exist |
We'll proceed with adding a |
…ng from creation Fix some random InvalidInternetGatewayID.NotFound errors
…ng from creation (hashicorp#6105) * Issue hashicorp#2174 Check that InternetGateway exists before returning from creation Fix some random InvalidInternetGatewayID.NotFound errors * Issue hashicorp#2174 Reuse IGStateRefreshFunc * Issue hashicorp#2174 Need to wait for creation before setting tags
Fix some random InvalidInternetGatewayID.NotFound errors
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. |
When I try to bootstrap a non-trivial infrastructure with an IGW, I sometimes run into the following error:
I noticed that for some resources we check if these are created after we send the request for creating before doing anything else, so I guess similar approach may need to be applied here.
// btw. the same infrastructure works well on second run of
terraform apply
The text was updated successfully, but these errors were encountered: