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

Instance with inline boot_disk and initialize_params breaks on type pd-ssd #292

Closed
nodesocket opened this issue Aug 3, 2017 · 6 comments
Labels
forward/review In review; remove label to forward service/compute-instances

Comments

@nodesocket
Copy link
Contributor

nodesocket commented Aug 3, 2017

Terraform Version

v0.10.0

Affected Resource(s)

google_compute_instance

Terraform Configuration Files

variable "zones" {
    type = "list"
    default = [
        "us-west1-a",
        "us-west1-b",
        "us-west1-c"
    ]
    description = "The zones to provision into"
}

resource "google_compute_instance" "rethinkdb" {
    count = 3
    name  = "rethinkdb${count.index + 1}"
    machine_type = "f1-micro"
    zone = "${element(var.zones, count.index)}"

    tags = ["rethinkdb"]

    boot_disk {
        initialize_params {
            image = "rethinkdb-ubuntu-1604-lts"
            type  = "pd-ssd"
            size = 10
        }
        auto_delete = true
    }

    network_interface {
        network = "default"
        access_config {
            # ephemeral external ip address
        }
    }

    scheduling {
        preemptible = false
        on_host_maintenance = "MIGRATE"
        automatic_restart = true
    }
}

Expected Behavior

This should create instances with each having a 10GB SSD boot disk using the image rethinkdb-ubuntu-1604-lts.

Actual Behavior

  • google_compute_instance.node.0: Error creating instance: googleapi: Error 400: Invalid value for field 'resource.disks[0].initializeParams.diskType': 'pd-ssd'. The URL is malformed., invalid
@rileykarson
Copy link
Collaborator

Thanks for the report @nodesocket!

We didn't catch this issue before our last provider release, but #275 appears to have fixed it and added a test so we can prevent something similar happening in the future. If this bug happens again after the next Google provider release, feel free to re-open the issue.

@nodesocket
Copy link
Contributor Author

@rileykarson does #275 also fix #218 (comment)?

@rileykarson
Copy link
Collaborator

I don't believe so; that will need to be made as a separate change.

@nodesocket
Copy link
Contributor Author

@rileykarson any idea when this fix will ship? Also, what is the process of updating a Terraform plugin? Is it just terraform init again?

@rosbo
Copy link
Contributor

rosbo commented Aug 14, 2017

We should a new version of the google provider in a week or so.

Yes, terraform init will fetch the latest google gcp provider.

@ghost
Copy link

ghost commented Mar 31, 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 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 ghost locked and limited conversation to collaborators Mar 31, 2020
@github-actions github-actions bot added forward/review In review; remove label to forward service/compute-instances labels Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
forward/review In review; remove label to forward service/compute-instances
Projects
None yet
Development

No branches or pull requests

3 participants