AWS EFS file system resource error after deletion

[attenda-pjaquenoud]

Terraform Version

Terraform v0.6.16 ( on Centos 6.7 )

Affected Resource(s)

aws_efs_file_system

Behaviour

Creating an aws_efs_file_system resource through terraform, then deleting in the AWS console, then running terraform again reports an error, whereas it should recreate the resource as per other resources.

Steps to Reproduce

1. terraform apply
2. Delete resource via the AWS console
3. terraform apply

Error refreshing state: 1 error(s) occurred:

* aws_efs_file_system.file_system: FileSystemNotFound: File system 'fs-9d739e54' does not exist.
        status code: 404, request id: d505a682-3ec7-11e6-81d3-1d41202f0881

Simple Test Case

resource "aws_vpc" "vpc" {
    cidr_block = "192.168.0.0/21"
}

resource "aws_subnet" "publicAzA" {
    vpc_id = "${aws_vpc.vpc.id}"
    availability_zone = "eu-west-1a"
    cidr_block = "192.168.0.0/24"
}

resource "aws_efs_file_system" "file_system" {
  tags { Name = "TestFS" }
}

Workaround

Remove the resource by editing the .tfstate

[ghost]

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.