-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Terraform crashes with nil context when making requests #6877
Comments
I'm unable to reproduce this using the datasource alone or in your provided config. Do other datasources and resources work? Does it work differently if you specify a different network? The panic appears to be related to a context that's set to |
What other information would be helpful ? |
now it crashed on apply
|
Thanks! That second log matches my theory that it wasn't an error specific to the datasource itself, but is an issue as the provider level. This has nothing to do with the description on the resource- I've essentially never included one personally.
A context is a Go object that's used to communicate information about an event, often an asynchronous one like a web request. The information passed along most often is a deadline for a request, or whether the request / series of requests has been cancelled by the sender. The Terraform provider receives a context from Terraform Core (the In case it's something else, are you running Terraform in an atypical environment? I saw a warning in the logs I didn't recognise and one of the only other issues I found when searching for it is hashicorp/terraform-provider-azurerm#7289. The specific message in the logs is |
Thanks! The linked Azure issue mentioned an atypical environment, so I was wondering if that was the case here. Turns out we also recently got another issue with the same message and error: #6887 Would you mind trying an older provider version to see if it's affected as well? |
3.31 also crashed
|
Thanks for all the context! We've identified a potential fix, although nobody on my team has been able to reproduce the issue. We'll merge it- GoogleCloudPlatform/magic-modules#3800 and push it through to the next valid release. Even if it isn't ultimately the fix, it's harmless to add either way. That should release as part of |
Thanks. |
I can confirm that 3.30.0 version worked for me! So, there's something wrong with the 3.32.0. I had this issue previously #6887 |
Same panic error i got with provider version 3.32.0, after downgrade to 3.30.0 looks fine. |
@rileykarson 3.34 did not crash. I will close |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
$ terraform -version 127 ↵
Terraform v0.12.29
Affected Resource(s)
data source * google_compute_network
Terraform Configuration Files
https://gist.github.com/longwuyuan/d764ed0f671f55b1239138fc915c0e11
Panic Output
https://gist.github.com/longwuyuan/d764ed0f671f55b1239138fc915c0e11
Expected Behavior
Terraform plan should be returned
Actual Behavior
Terraform crashes with error as
Error: rpc error: code = Unavailable desc = transport is closing
Steps to Reproduce
terraform init
terraform plan
Important Factoids
References
The text was updated successfully, but these errors were encountered: