-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Hidden error message if aws_vpc_ipam_pool_cidr
fails
#25192
Comments
aws_vpc_ipam_pool_cidr
throws an erroraws_vpc_ipam_pool_cidr
fails
Thanks for opening this up. I'll take a look and see if i can expose the true error |
@nitrocode one thing to note is that That being said, the type IpamPoolCidr struct {
_ struct{} `type:"structure"`
// Details related to why an IPAM pool CIDR failed to be provisioned.
FailureReason *IpamPoolCidrFailureReason `locationName:"failureReason" type:"structure"`
}
type IpamPoolCidrFailureReason struct {
_ struct{} `type:"structure"`
// An error code related to why an IPAM pool CIDR failed to be provisioned.
Code *string `locationName:"code" type:"string" enum:"IpamPoolCidrFailureCode"`
// A message related to why an IPAM pool CIDR failed to be provisioned.
Message *string `locationName:"message" type:"string"`
} terraform-provider-aws/internal/service/ec2/ipam_pool_cidr.go Lines 100 to 102 in 19d5b4c
the This is a good beginner issue so im going to float it around to see if anyone wants. If not, ill fix it in the near future |
I am looking at this issue |
closed by #25287 |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
aws_vpc_ipam_pool_cidr
Terraform Configuration Files
https://github.com/aws-ia/terraform-aws-ipam/blob/main/modules/sub_pool/main.tf
Debug Output
Panic Output
N/A
Expected Behavior
Clear error thrown during plan time check
Actual Behavior
Apply successfully or at the very least, expose the real error message
From the UI, it appears that the error happens because the cidr
10.96.0.0/12
is not within10.0.0.0/11
. This is probably something that we could calculate as a plan level check before even hitting the AWS API.Steps to Reproduce
terraform apply
Important Factoids
N/A
References
N/A
The text was updated successfully, but these errors were encountered: