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

Upgrade from v0.12.25 to v0.13 problem with decoded from the state #25924

Closed
omerh opened this issue Aug 19, 2020 · 4 comments
Closed

Upgrade from v0.12.25 to v0.13 problem with decoded from the state #25924

omerh opened this issue Aug 19, 2020 · 4 comments
Labels
bug duplicate issue closed because another issue already tracks this problem new new issue not yet triaged

Comments

@omerh
Copy link

omerh commented Aug 19, 2020

Terraform Version

Terraform v0.13.0
+ provider registry.terraform.io/-/aws v3.2.0
+ provider registry.terraform.io/hashicorp/aws v3.2.0

Trying to run a plan from version 0.12 with version 0.13.
Backend state is s3 with encryption

terraform {
  backend "s3" {
    bucket  = "-------------------------"
    key     = "-----------------/----------------------.tfstate"
    region  = "us-east-1"
    encrypt = true
    profile = "mm"
  }
}

I ran terraform init and all went well

When running the plan I get an error:

Error: Invalid resource instance data in state

  on ../../modules/aws/eks/nodes_role/main.tf line 69:
  69: resource "aws_iam_instance_profile" "eks_nodes" {

Instance module.eks_role.aws_iam_instance_profile.eks_nodes data could not be
decoded from the state: unsupported attribute "roles".
@omerh omerh added bug new new issue not yet triaged labels Aug 19, 2020
@mildwonkey
Copy link
Contributor

Hi @omerh , thanks for reporting this! It is a duplicate of #25752, and the fix will be in the next terraform release!

@mildwonkey mildwonkey added the duplicate issue closed because another issue already tracks this problem label Aug 19, 2020
@omerh
Copy link
Author

omerh commented Aug 20, 2020

Thanks @mildwonkey please note that the version on #25752 is on version v0.13.0-rc1 and I am on version v0.13.0

@mildwonkey
Copy link
Contributor

Yes - the problem remained in v0.13.0 and the fix is in terraform v0.13.1, which we plan on releasing next week! Thanks and sorry!

@ghost
Copy link

ghost commented Oct 11, 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.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate issue closed because another issue already tracks this problem new new issue not yet triaged
Projects
None yet
Development

No branches or pull requests

2 participants