-
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
Compute instance IP addresses are not detected #519
Comments
I can confirm this started to happen recently in my google provider being run on my CI system.
this is my instance configuration:
|
I have learned that I can work around it by setting up a google_compute_address and assigning it to the network_interface.access_config.nat_ip stanza. At that point I can use the nat_ip in the DNS entry, instead. |
Thanks, I might do that until bug is fixed |
Probably a bug in plugin 1.0.1 and 1.0.0
|
I can confirm issue and workaround. |
I just created environment with
Tried reinitialize the environment with older version of provider provider "google" {
credentials = "${file("${module.shared-vars.gce_service_account_file}")}"
project = "${module.shared-vars.gce_project_id}"
region = "${module.shared-vars.gce_region}"
version = "0.1.3"
} but I get following errors when I refresh terraform output
Luckily I found this issue here |
I've experienced this as well: computed attributes under network_interface aren't being saved to the state. I'm pretty sure the problem is with f2f276e#diff-6ebc1a840e42235a51a46d537f17ddaa, which I think had an unintended side-effect of causing the network_interface attributes to not get copied from the Google cloud API response back to the Terraform state. If I'm correct it's a one-line fix; if I can figure out the unit testing before one of the Hashicorp devs beat me to it then I'll try submitting a pull request. |
<!-- This change is generated by MagicModules. --> /cc @rhalat
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! |
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/savannidgerinel/6e4ec396a78900a4d242d15588fca00b
Expected Behavior
I expected this command to complete having created one DNS zone, one compute instance, and a DNS entry for that compute instance.
Actual Behavior
The zone and compute instance were both created. The DNS entry was not created and the error indicated that the referenced IP address was not set:
The state also shows a lot of empty
network_interface
fields.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
This was largely lifted from the terraform GCS documentation except for the server and DNS names.
References
The text was updated successfully, but these errors were encountered: