-
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
Error on terraform apply for a 7.5MB AWS lambda but OK when 5MB: ResourceConflictException #11708
Comments
I experienced a similar issue, but it disappeared when switching to a more reliable network connection. |
I've had the exact same issue (TF 0.12.9 and 0.12.24, AWS Provider 2.61.0) with an 8MB lambda zip: it deploys successfully to AWS, but Terraform fails by saying that it already exists during the request to create it in the first place. At that point it is invisible to TF and I have to delete it from the AWS console. I tried with a much, much smaller zip and it created fine, and then did an This was repeated a couple of times with the same result |
I am having exactly the same issue! It looks like the debug output above got truncated. Here's mine, with identifiers and large base64 blobs obfuscated: https://gist.github.com/meustrus/8d78e6f6fd4124413ae8531febaf68e2 Looking at the logs, for some reason it starts a second seemingly identical call to This is my resource (real names obfuscated):
|
I've had the exact same issue, my file was 11mb. For anyone looking for a workaround this worked for me. I used the
|
I am still experiencing this issue, but only on a slower connection. It seems to create the lambda successfully as long as it finishes uploading within 90 seconds. Could this be a strange regression of #4516? |
Also having this issue on a slower connection. Lambda function is created, but getting an error "Function already exist" |
Hey y'all 👋 Thank you for taking the time to file this issue, and for the continued discussion around it. Given that there's been a number of AWS provider releases since the last update, can anyone confirm whether you're still experiencing this behavior? |
This issue was originally opened by @frediana as hashicorp/terraform#23887. It was migrated here as a result of the provider split. The original body of the issue is below.
Hello,
I have a this very simple use case I'm trying to make work for hours now without any success.
I have a simple lambda (written in Go) that is zipped 7.5MB big. A lambda is eventually created into my account (and works). But terraform is somehow try to re-create the same lambda again, and fails (because the lambda already exists)
It seems to be related to the size of this archive somehow. When I try with a smaller archive (around 5MB) everything works fine.
Is there any workaround, limitation or any clue about this issue?
Thanks
Adrien
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/frediana/606331547ca66d41e658449032e63ad4
Crash Output
https://gist.github.com/frediana/24e0c3454271afa88588b95cf7d99372
Expected Behavior
A lambda should be created successfully and terraform apply should not end up with an error.
Actual Behavior
Lambda is created/uploaded to AWS because but terraform crash.
Steps to Reproduce
terraform init
terraform apply
Additional Context
The function I try to create is a 7.5MB zip, Golang binary.
The text was updated successfully, but these errors were encountered: