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

tf0.13.0 Invalid resource instance data in state (aws_instance) #25897

Closed
julienpierini opened this issue Aug 18, 2020 · 2 comments
Closed

tf0.13.0 Invalid resource instance data in state (aws_instance) #25897

julienpierini opened this issue Aug 18, 2020 · 2 comments
Labels
bug duplicate issue closed because another issue already tracks this problem

Comments

@julienpierini
Copy link

Hi,

Since the new terraform version 0.13.0, I get an error on plan, destroy and apply.

I use the public module : https://github.com/terraform-aws-modules/terraform-aws-ec2-instance (version 2.0 and 2.15)
config used :

terraform {
  required_version = ">= 0.13.0, < 0.14"

  required_providers {
    aws = ">= 3.0, < 4.0"
  }
}

Error message :

Error: Invalid resource instance data in state

  on .terraform/modules/ec2/terraform-aws-ec2-instance-2.15.0/main.tf line 5:
   5: resource "aws_instance" "this" {

Instance module.ec2.aws_instance.this[0] data could not be decoded from the
state: unsupported attribute "network_interface_id".

Resolution :
Use prior version of terraform, works with 1.29.0 :

terraform {
  required_version = ">= 0.12.9, < 0.14"

  required_providers {
    aws = ">= 3.0, < 4.0"
  }
}
@julienpierini julienpierini added bug new new issue not yet triaged labels Aug 18, 2020
@mildwonkey mildwonkey added duplicate issue closed because another issue already tracks this problem and removed new new issue not yet triaged labels Aug 19, 2020
@mildwonkey
Copy link
Contributor

Hi @julienpierini , I'm sorry you're experiencing this behavior.

This appears to be a duplicate of #25752, which has been fixed. The fix will be included in v0.13.1, which is not yet released but we expect to do so next week.

If you still have a problem after the next release, please open a new issue. Thank you!

@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
Projects
None yet
Development

No branches or pull requests

2 participants