-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: aws_vpc_ipam_pool_cidr_allocation returns inconsistent results #29045
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @pguinard-public-com 👋 Thank you for taking the time to raise this! A fix for this has just been merged, and will go out with the release later this week. Given that, I'll go ahead and close this issue. If you think I've done this in error, please do let me know. |
This is what I get for searching open issues! 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. |
Terraform Core Version
1.3.7
AWS Provider Version
4.51.0
Affected Resource(s)
Expected Behavior
cidr, ipam_pool_allocation_id,
terraform console
Acquiring state lock. This may take a few moments...
Actual Behavior
Actual behavior (sometimes):
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Where the error occurs:
Setup in a different AWS account:
Steps to Reproduce
Run terraform apply / destroy / apply / destroy / apply / destroy until the error is triggered.
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: