-
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 Plan crashes when there are changes to existing resources #4770
Comments
Which resource? This looks very similar to #4756 for which a fix was just merged. |
@tysen Thanks for the quick response. Just a quick update: I have tried using the Google Beta Provider 2.17 as many people mentioned it in #4756, but I get the same crash. I could not pin-point the issue to a specific resource but, if I can assume that the last resource shown in the log before the crash is the culprit, then it should be: google_compute_global_forwarding_rule of the Google Provider ( Tested with 2.13 and 2.18 ).
|
Can you provide an example config so I can reproduce this behavior? |
@Gustavo-Benitez, |
@venkykuberan Thank you. I cannot provide the code however, upgrading to terraform 0.12.18 and using Google Provider 2.19 seems to have had a positive effect. I believe the resource that was corrupt on every state file was the Google Provider compute_global_forwarding_rule |
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
Terraform Version
Terraform v0.12.12
Affected Resource(s)
plugin.terraform-provider-google_v2.18.0_x4
Debug Output
Panic Output
Expected Behavior
Terraform should have generated a plan or an error should have been produced if the plan could not be generated.
Actual Behavior
Terraform crashed when running a plan
Steps to Reproduce
Important Factoids
The same issue was observed using:
References
The text was updated successfully, but these errors were encountered: