-
Notifications
You must be signed in to change notification settings - Fork 9.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 reading EC2 Network ACL Rule #23142
Comments
@cdancy Thanks for raising this issue.
terraform-provider-aws/internal/service/ec2/find.go Lines 773 to 778 in 7a06646
terraform-provider-aws/internal/service/ec2/find.go Lines 722 to 723 in 7a06646
terraform-provider-aws/internal/service/ec2/find.go Lines 740 to 743 in 7a06646
|
@ewbankkit just started trying out |
I'm seeing a similar pattern using AWS provider 4.5.0.
It appears to be intermittent though. |
+1 Behaviour: Already NACL had nearly 10 rules and while adding new rules (2 ingress and 2 egress) faced the issue for 1st ingress. However in the UI of AWS, I see all new 4 rules were added. I have tried to re-run to make the state consistent and below is the output Plan: 1 to add, 0 to change, 1 to destroy. Output : Ingress rule 110 was deleted and don't see any addition of the rule 110 So I have rerun the apply to add this rule and this time it has added the rule |
+1 on getting the "empty result" for nacl association |
Still seeing this regularly on AWS provider v4.39 |
Yes, and it's a super frustrating error for running smooth pipelines |
I'm also seeing this using provider ver 4.15.1 |
It is quite an annoying error. Reran the plan, the plan out indicated the associations would be replaced. The associations were created successfully after, maybe multiple times, replan/reapply.
|
@tigerpeng2001 yeah we have a wrapper script that basically retries upon some failure message encountered. Usually after a handful of retries, with some waits thrown in between for good measure, things go through. Kind of ridiculous solution but it does work 90% of the time |
This functionality has been released in v4.59.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. |
Now that THIS ISSUE has finally been resolved we are now seeing this which looks similar and I'm wondering if the same logic can be applied?
The text was updated successfully, but these errors were encountered: