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

Error: Incorrect attribute value type deploying on AWS with Terraform #463

Closed
edernucci opened this issue May 23, 2019 · 5 comments · Fixed by #466
Closed

Error: Incorrect attribute value type deploying on AWS with Terraform #463

edernucci opened this issue May 23, 2019 · 5 comments · Fixed by #466
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Milestone

Comments

@edernucci
Copy link

edernucci commented May 23, 2019

What happened:
Error running terraform plan.

What is the expected behavior:
terraform plan should execute without errors.

How to reproduce the issue:

$ terraform plan

Error: Incorrect attribute value type

  on main.tf line 180, in resource "aws_lb" "control_plane":
 180:   subnets            = ["${local.all_subnets}"]

Inappropriate value for attribute "subnets": element 0: string required.

Anything else we need to know?
Using files from https://github.com/kubermatic/kubeone/tree/master/examples/terraform/aws

$ terraform version
Terraform v0.12.0
+ provider.aws v2.11.0
$ cat terraform.tfvars 
cluster_name = "demo"
aws_region = "sa-east-1"

Information about the environment:
KubeOne version (kubeone version):

$ kubeone version
{
  "kubeone": {
    "major": "0",
    "minor": "6",
    "gitVersion": "0.6.2",
    "gitCommit": "7b86c3bf654366a64da608c7b710360dd5f5d777",
    "gitTreeState": "",
    "buildDate": "2019-05-13T16:49:50Z",
    "goVersion": "go1.12.5",
    "compiler": "gc",
    "platform": "linux/amd64"
  },
  "machine_controller": {
    "major": "1",
    "minor": "1",
    "gitVersion": "v1.1.5",
    "gitCommit": "",
    "gitTreeState": "",
    "buildDate": "",
    "goVersion": "",
    "compiler": "",
    "platform": "linux/amd64"
  }
}

Operating system:

$ uname -a
Linux artorias 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux

Provider you're deploying cluster on:
AWS
Operating system you're deploying on:
Linux

@edernucci edernucci added the kind/bug Categorizes issue or PR as related to a bug. label May 23, 2019
@kron4eg
Copy link
Member

kron4eg commented May 23, 2019

Thanks for the report, terraform 0.12 just got release and it seems like out example terraform configs are only 0.11 compatible (despite terraform 0.12checklist claimed otherwise). Most likely we going to copy existing configs and make copies 0.12 compatible, but that'll take some time.

@edernucci
Copy link
Author

@kron4eg

This was my first experience with Terraform, so I thought I was doing something wrong.

In this case if I use version 0.11 everything should work smoothly?

@kron4eg
Copy link
Member

kron4eg commented May 23, 2019

yeah, we use 0.11 terraform in out e2e tests and it works quite well for us.

@edernucci
Copy link
Author

@kron4eg

Just for clarification, I downgraded Terraform, cleaned the directory and started again.

Everything worked as expected with version 0.11.14.

Thanks for your support.

@xmudrii xmudrii added this to the v0.9 milestone May 31, 2019
@xmudrii xmudrii added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label May 31, 2019
@eqrx
Copy link
Contributor

eqrx commented Jun 17, 2019

@edernucci Terraform 0.12 support have just been merged and will be available with the 0.9 release (Should come around the end of this week)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants