Skip to content
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

google-cloud provider fails to look up family correctly #9229

Closed
dvianello opened this issue Oct 5, 2016 · 1 comment · Fixed by #9243
Closed

google-cloud provider fails to look up family correctly #9229

dvianello opened this issue Oct 5, 2016 · 1 comment · Fixed by #9243

Comments

@dvianello
Copy link

Terraform Version

Terraform v0.7.4

Affected Resource(s)

  • google_compute_instance

Terraform Configuration Files

provider "google" {
  region = "europe-west1"
}

resource "google_compute_instance" "test_vm" {
  name         = "test-vm"
  machine_type = "n1-standard-4"
  zone         = "europe-west1-b"

  disk = {
    image = "ebi-centos-7"
    type  = "pd-ssd"
  }

  # Network interface
  network_interface {
    subnetwork = "default"
  }
}

Debug Output

https://gist.github.com/dvianello/c9fa1f00ec1c342a9197d5eccd9dc49a

Expected Behavior

Terraform find the latest version of the private image belonging to the (private) ebi-centos-7 family and uses that to launch the VM.

Actual Behavior

Terraform fails claiming that there's no such family. However, as visible by the logs, it's actually trying to look up for that image name in the centos-cloud project, not the local project. The error goes away pre-pending the project name to the image name like 'image = "project-name/ebi-centos-7'. Images contained in the ebi-centos-7 family are baked starting from the centos-cloud/centos-7 family, of course.

Steps to Reproduce

  1. terraform apply

Important Factoids

Not really.

@ghost
Copy link

ghost commented Apr 20, 2020

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.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants