Skip to content
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: Wait for NACL rule to be visible #4734

Merged
merged 1 commit into from
Jan 22, 2016

Conversation

jen20
Copy link
Contributor

@jen20 jen20 commented Jan 19, 2016

Fixes #4721. It seems there may be some eventual consistency in the API for network ACLs. This fix doesn't use resource.WaitForState() as there the NACL is not something that can be looked up by ID and has a property which determines if it is present.

Instead we reuse the findNetworkAclRule function which the Read function exhibiting the problem uses, and retry over a 3 minute period, returning an error message informing the user that running terraform apply again will likely allow them to continue.

@catsby Not sure if there is any precedent for this approach, or whether you have previously wrangled resource.WaitForState() to do the correct thing to meet the same ends? It does feel somewhat like we should be counting on the resource to be created at some point rather than timing out.

Fixes #4721. It seems there may be some eventual consistency in the API
for network ACLs. This fix doesn't use resource.WaitForState() as there
the NACL is not something that can be looked up by ID and has a
property which determines if it is present.

Instead we reuse the findNetworkAclRule function which the Read function
exhibiting the problem uses, and retry over a 3 minute period, returning
an error message informing the user that running `terraform apply` again
will likely allow them to continue.
@catsby
Copy link
Contributor

catsby commented Jan 21, 2016

It's too bad this is necessary 😦
This looks good to me. To answer your question, no, I don't believe there is precedent here

🚢

catsby added a commit that referenced this pull request Jan 22, 2016
provider/aws: Wait for NACL rule to be visible
@catsby catsby merged commit 6befb71 into master Jan 22, 2016
@jen20 jen20 deleted the b-network-acl-visibility branch January 22, 2016 20:27
@ghost
Copy link

ghost commented Apr 28, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws_network_acl_rule: Transient error on creation
2 participants