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

refreshing aws_elasticache_subnet_group fails if resource does not exist #7062

Closed
joshgarnett opened this issue Jun 8, 2016 · 2 comments · Fixed by #7075
Closed

refreshing aws_elasticache_subnet_group fails if resource does not exist #7062

joshgarnett opened this issue Jun 8, 2016 · 2 comments · Fixed by #7075

Comments

@joshgarnett
Copy link

joshgarnett commented Jun 8, 2016

$ terraform -v
Terraform v0.6.16
Error refreshing state: 1 error(s) occurred:

* aws_elasticache_subnet_group.redis: CacheSubnetGroupNotFoundFault: Cache subnet group foo-bar not found.
    status code: 400, request id: d3329895-2d0a-11e6-855e-4b99d85a5fe7

I'm guessing it's just a matter of handling the failure case properly. SQS had a similar issue at #6381

stack72 added a commit that referenced this issue Jun 8, 2016
…d exception

Fixes #7062

make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSElasticacheSubnetGroup'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /vendor/)
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSElasticacheSubnetGroup -timeout 120m
=== RUN   TestAccAWSElasticacheSubnetGroup_basic
--- PASS: TestAccAWSElasticacheSubnetGroup_basic (44.62s)
=== RUN   TestAccAWSElasticacheSubnetGroup_update
--- PASS: TestAccAWSElasticacheSubnetGroup_update (73.74s)
PASS
ok  	github.com/hashicorp/terraform/builtin/providers/aws	118.379s
@stack72
Copy link
Contributor

stack72 commented Jun 8, 2016

Hi @joshgarnett

Thanks for reporting this issue. I just opened a PR that should fix it :)

This should be included in Terraform 0.7

Paul

@ghost
Copy link

ghost commented Apr 25, 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 and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants