Terraform: Crash during plan/apply

[rafi-greenberg]

Terraform Version

Terraform v0.12.6
+ provider.google v2.13.0
+ provider.google-beta v2.13.0
+ provider.mongodbatlas (unversioned)
+ provider.null v2.1.2
+ provider.template v2.1.2

Terraform Configuration Files

Not sure what's causing this crash so i'll just post the logs

Debug Output

Crash Output

Error: rpc error: code = Unavailable desc = transport is closing
Error: rpc error: code = Unavailable desc = transport is closing
Error: rpc error: code = Unavailable desc = transport is closing

panic: runtime error: invalid memory address or nil pointer dereference
2019-08-20T09:38:58.824-0700 [DEBUG] plugin.terraform-provider-google-beta_v2.13.0_x4: [signal SIGSEGV: segmentation violation code=0x1 addr=0x21 pc=0x19a9727]
2019-08-20T09:38:58.824-0700 [DEBUG] plugin.terraform-provider-google-beta_v2.13.0_x4:
2019-08-20T09:38:58.824-0700 [DEBUG] plugin.terraform-provider-google-beta_v2.13.0_x4: goroutine 90 [running]:

Full crash.log here:
https://gist.github.com/75c008f0b7da9630c7707258e7c82b87

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

[rafi-greenberg]

Can anyone help? I'm totally stuck here... would reverting to a previous build or provider allow me to run terraform?

[umegaya]

@mackoftrack I had almost same problem yesterday. did you use google_sql_database_instance resource and specify "" for settings.backup_configuration.start_time?

investigation with hand crafted terraform-provider-google reveals recent days (probably within a week), this setting start to crash at https://github.com/terraform-providers/terraform-provider-google/blob/master/vendor/github.com/hashicorp/terraform/terraform/diff.go#L522 because diff become <nil>, I suspect that some minor change of google API response causes buggy behaviour of terraform diff logic.

for my case, setting proper value ("HH:MM" format) to settings.backup_configuration.start_time magically stops this crash. hope this helps 👍

[rafi-greenberg]

@umegaya Thanks! That seemed to do the trick!

[jbardin]

Closed by #22690

[hashibot[bot]]

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.