Skip to content
This repository has been archived by the owner on Dec 10, 2021. It is now read-only.

wait_for_instances invalid or unknown key #34

Open
bizmate opened this issue May 14, 2018 · 4 comments
Open

wait_for_instances invalid or unknown key #34

bizmate opened this issue May 14, 2018 · 4 comments

Comments

@bizmate
Copy link

bizmate commented May 14, 2018

$ TF_LOG=DEBUG TF_LOG_PATH=tf.log terraform0.11.2 plan --var-file=../../data/app/app-prototype/common.tfvars

Error: module.nat.module.nat-gateway.google_compute_instance_group_manager.default: : invalid or unknown key: wait_for_instances

with

$ terraform0.11.2 -v
Terraform v0.11.2
+ provider.google v1.5.0
+ provider.null v1.0.0
+ provider.random v1.2.0
+ provider.template v1.0.0

Is this due to terraform version?

@joelchrist
Copy link

joelchrist commented Jun 27, 2018

I have the exact same issue:

Terraform v0.11.7
+ provider.dnsimple v0.1.0
+ provider.google v1.7.0
+ provider.kubernetes v1.0.1
+ provider.null v1.0.0
+ provider.template v1.0.0

Using the module as follows:

module "nat" {
  source     = "GoogleCloudPlatform/nat-gateway/google"
  region     = "${var.region}"
  network    = "default"
  subnetwork = "default"
}

where ${var.region} is europe-west1

@AndrewFarley
Copy link
Contributor

That is a more recent feature of the Google provider for terraform. I'd advise both of you to just update your google provider. Easiest way to do this is...

rm -i .terraform/plugins/*/terraform-provider-google*
terraform init

It will prompt you before deleting a file, which it should have a prompt similar to...

remove .terraform/plugins/darwin_amd64/terraform-provider-google_v1.14.0_x4? n

Do this and try again, I assure you this problem will go away. So far as I know there are no breaking changes with the google provider, so you shouldn't see any other changed functionality in your stacks.

@joelchrist
Copy link

@AndrewFarley Thanks for your help, that worked. Do you by any chance have a clue as to what is my problem now:

Using most kubectl commands results in the following error:

Error from server: Get https://10.132.0.6:10250/containerLogs/default/example/example: No SSH tunnels currently open. Were the targets able to accept an ssh-key for user "gke-27c65ac9ee93fb9a3863"?

Do you know what could be causing this?

@AndrewFarley
Copy link
Contributor

Without detailed information, your TF files, and a general idea of what you're actually trying to do, no idea. Haven't seen that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants