Terraform Crashes while creating VM within VPC in Google Cloud #586
Comments
|
Hey @naoleyrashmi, are you creating the VPC in the other module at the time of the crash or has it already been created? Without actually looking at the logs, I wonder whether the instance is trying to be created when the network hasn't been finished creating since you're referring to it by variable name rather than interpolation. |
|
hello @danawillow, VPC has already been created in some other module and then passing the value of network in current module via variable. Moreover its worth noticing that when an instance and VPC are created within same module this issue is not faced. Also i get below error while trying to apply the changes: Error applying plan: 1 error(s) occurred:
Terraform does not automatically rollback in the face of errors.
!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!! Terraform crashed! This is always indicative of a bug within Terraform. When reporting bugs, please include your terraform version. That !!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!! |
|
Hey, The last time it worked for me with the exact same configuration is last Thursday. Terraform Version: 0.10.7 I use terraform to spin up environments at will, versions of this setup have worked before, the only thing that changes are the disk images reference. Useful Factoids:I'm launching this build from a docker image that hasn't changed and terraform init is done prior to planning and applying. After checking the account, all the resources are created (the ones that are marked as failed) the dependant resource are not create which is logic. Could it be some API change on Google's part that makes this crash ? |
|
I'm pretty sure you're both experiencing #553, which was fixed in v1.0.1 of the google provider. Try upgrading and let me know how it goes. In the meantime, I'm going to close this issue (since I think it's a duplicate) but please do let me know if upgrading doesn't fix the problem. |
|
@danawillow I did try upgrading but unfortunately it didn't work. Can you please suggest way forward to resolve this. Moreover it seems #553 is already closed , whereas i am still facing issue. |
|
@naoleyrashmi mind sending me another set of debug logs? That'll help me with line numbers and such. |
|
@danawillow i am no more facing this issue. You might close this case. Thanks for your help. |
…#586) <!-- This change is generated by MagicModules. --> Original Author: @rileykarson
|
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! |
ghost
locked and limited conversation to collaborators
github-actions
bot
added
forward/review
Terraform Version
v0.10.7
Affected Resource(s)
Please list the resources as a list, for example:
-google_compute_network
Terraform Configuration Files
resource "google_compute_instance" "default" {
name = "test"
machine_type = "n1-standard-1"
zone = "us-east1-c"
tags = ["test1", "vm"]
boot_disk {
initialize_params {
image = "debian-cloud/debian-8"
}
}
network_interface {
network = "${var.testvpc_id}"
}
}
Few Pointers:
Crash Output
crash.log
crash.log
Expected Behavior
A VM to be created within VPC
Actual Behavior
Terraform crashed
Steps to Reproduce
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: