plugin.(*GRPCProvider).ValidateResourceConfig request was cancelled. #20274
Comments
github-actions
bot
added
needs-triage
|
Any update? |
|
Also seeing similar issue with TF 1.0.0 and provider 3.51.0, and it seems to be intermittent and the error messages vary. Ones we've seen are: And: |
breathingdust
added
bug
YakDriver
added
the
crash
|
I'm seeing the same error messages. Terraform 1.0.8 and AWS provider 3.61.0. The errors are intermittent. Interestingly I'm getting them from a validate in my CI (AWS CodeBuild), i.e. |
|
In our environment, we found this to be because Terraform ran out of memory in the memory cgroup it was in. If you're on Linux, you can look in the kernel logs to see if its killing the provider process due to memory issues. For whatever reason, Terraform seems to use quite a lot of memory when it loads providers. If you have multiple providers instantiated in the same workspace, you need a lot of memory. |
|
We had this error with custom resource definition inside of kubernetes_manifest. What fixed it for us was to add an empty additionalPrinterColumn in the manifest: log output |
Based on the suggestion from @jcmcken I increased the size of the compute type in CodeBuild to provide more memory and haven't seen the error since. 👍 |
|
Freeing up memory on my local M1 mac dev environment made this intermittent issues. |
|
I'm running an M1 Max based MacBook Pro with 32GB of ram and have been randomly hitting this issue when using even small (3-4 resource) terraform plans and applies through terragrunt. Once the issue occurs it seems to repeat until I run a
|
|
Another m1 user here. |
|
9 months later, why are we still required to work around this problem? |
|
@jorhett This issues only occurs if you are running the amd64 binaries of terraform on the M1. If you move to the arm64 (native) binaries the issue goes away. The problem must be somewhere in the arm64 / amd64 translation layer. |
I'm not sure this is correct? Looks like multiple people in the thread are using Linux (including the OP). We've experienced similar with Linux as well. Looks like there may be a mixture of two different issues (Linux and generally high memory usage, and Darwin |
This is not true. I'm using the arm64 binaries exclusively. Terraform and the plugins are all arm64. |
|
Getting below error when tried to run terraform apply from the agent. Tried changing the provider version and didn't get any soultion. Please suggest github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0xc000b455e0, 0xa4cab58, 0xc002d313c0, 0xc002b45380, 0x8234060, 0xc000819500, 0x0, 0x0, 0x0) Error: The terraform-provider-aws_v3.73.0_x5 plugin crashed! This is always indicative of a bug within the plugin. It would be immensely |
I am running into the same issue. Any suggestions on this issue? Increasing memory made no difference in my case |
|
Still an issues guys!!! |
|
I'm running M1 16G ram and running into this issue Terraform v1.0.8
running |
I added |
You should be using |
|
I am using "arm64" binaries and providers. I have tried everything but I'm still getting follow errors. In past with aws providers lower version 3.61, everything was working. But when we upgraded it newer aws provider versions it keep failing. Just to fall back, I tried to setup amd64 arch but now it is also not working for me. ( but that is not a main concern now). |
|
I'm also using ARM64 binaries on an M1 MBP and the only fix I found was the export above. You can see at least three different errors and they come up intermittently. I got the GRPC error above as well as these other two. and |
|
SOLVED. The solution was to whitelist terraform.exe in the Trend Micro Anti Virus on the client computer. |
|
In my case w/ Docker containers in my Mac. I turned off my other containers and it suddenly worked properly |
|
We ran into this same issue, but when we increase the RAM available to atlantis, it became resolved. I think the issue is that golang behaves oddly when it's short of memory, as opposed to just OOM crashing. |
|
My setup was exactly as @paul-civitas comment, also atlantis and checking the metrics, we confirmed that the pod was reaching the memory limit |
How do we do that? I am facing this issue with Terraform Datadog provider with 3.26 version. |
|
I am seeing this error with Terraform Datadog provider: ⇒ terraform -v
|
|
Hit the same error. My system: TLDR Nothing I could see wrong. Removing statefile/lockfile/.terraform folder and hitting init again didn't fix it either. What worked for me: Thought I'll post it in case this approach helps someone else who's also confirmed/tried other things 😄 |
|
Mac M1 user here. Fixed by rebooting my computer and re-initializing terraform. |
|
This appears to have been resolved by some combination of:
I'm going to close this issue. If you are still experiencing this error, please open a new issue |
|
Upgrading terraform to the latest version, and using ARM64, seems to make this go away for us yes. |
|
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. |
and others
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform Version = 1.0.0
Terraform AWS Provider = 3.50.0
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
Actual Behavior
plugin.(*GRPCProvider).ValidateResourceConfig request was cancelled.
Steps to Reproduce
terraform planImportant Factoids
References
The text was updated successfully, but these errors were encountered: