Closed PratteekB closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Off the top of my head, the provider is running out of memory because it is attempting to log the binary contents of the Lambda function's ZIP file.
I suspect that ~any~* error the AWS Provider returns will cause Terraform/SDK to crash in a similar way. This only occurs as of v4.53.0
. The only change in v4.53.0
was #29223 (logging). (* Random golang errors
do not seem to cause this. Perhaps only AWS errors?)
I can reproduce the issue 100% in situations where the plugin returns an error. Whether you get fatal error: out of memory
or fatal error: concurrent map writes
seems to depend largely on whether the goroutines trip up first or memory runs out first. These may not be useful clues.
In case it is helpful, here is a complete (~4100 line) trace: https://gist.github.com/YakDriver/66b508dab3342da50b2da75f4b17a73a
@PratteekB, how large is the Zip file that you're sending? I'd like to test with something comparable
Hi @PratteekB, the latest version of the provider now truncates the log entries. This may address the out of memory error. If you are still seeing this error, please open a new issue and let us know the size of the Zip file that you're sending.
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.
Previously titled: "The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call."
Changing the name because at this stage I believe it is misleading since any (?) error may cause this crash.
See also #29236
Terraform Core Version
1.3.4
AWS Provider Version
4.52.0
Affected Resource(s)
unclear from the error message however the 2 plugins which errored were:
aws_rds_cluster_instance aws_lambda_function
Expected Behavior
the main.tf file was meant to execute as it has been and provision several AWS resources:
Actual Behavior
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
run 'terraform apply -auto-approve'
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
29223
29236
Would you like to implement a fix?
None