-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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-provider-google_v3.66.0_x5 plugin crashed #9022
terraform-provider-google_v3.66.0_x5 plugin crashed #9022
Comments
The same issue as above but with terraform 0.12.31 (upgrading due to public key invalidation).
I suspect it's a regression from 9 days ago: #8953 The And this change in the PR assumes that can be cast to an array
^ I could be wrong, does that sound about right? @edwardmedia |
Same issue on TFE .13.7 with this latest GCP 3.66 update:
|
Same as @rcaril but in Terraform v0.13.5 |
@megan07 - this code push did not fix the problem. Same behavior. |
Hi @rcaril, I'm sorry you're experiencing the issue still. Would you be willing to share your configuration and your full debug logs so I can see what is happening? Thanks! |
@megan07 My log is attached. run-mwzH4qRFxRLhDV4v-plan-log.txt What kind of configuration are you looking for? This is my initial setup:
Please let me know if you need more details. |
Thank you for the quick response @rcaril, I think there might be a small misunderstanding. The fix for this bug was recently merged and is still in the process of being released. From the configuration, it seems that you may still be using a version (3.66.0) that does not have this fix. The issue gets closed automatically when a fix is merged, which probably caused this confusion. Sorry about that. We are working to get this fix out in a release as soon as possible. |
Hi @aareet - thanks for clarifying this! I indeed did not realize that the merge would not go into your release automatically. Please keep me updated on when this has been released. Would I expect this to be version 3.67? |
Glad we figured it out 🙂. I will certainly update this ticket once we release. We're currently expecting this to be version 3.66.1, but I will confirm once we release. |
Hi folks, v3.66.1 with the fix for this issue is now available - please test with it and let us know if you have any feedback https://registry.terraform.io/providers/hashicorp/google/latest. Thanks for your patience. |
@aareet This has solved my problem, thanks! |
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 👉 hashibot-feedback@hashicorp.com. 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 v0.15.1
on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/dieseldesai/4f785a8da23b847165dc8eb04cab4c7c
Expected Behavior
A google compute instance should have been provisioned
Actual Behavior
the terraform google provider plugin crashed
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: