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

provider/aws: Fix DB Subnet refresh issue #1254

Merged
merged 1 commit into from
Mar 20, 2015
Merged

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Mar 19, 2015

Fixes #496 by updating the read function to mark the resource as deleted if not found.

@mitchellh
Copy link
Contributor

LGTM.

catsby added a commit that referenced this pull request Mar 20, 2015
provider/aws: Fix DB Subnet refresh issue
@catsby catsby merged commit d3135c1 into master Mar 20, 2015
@catsby catsby deleted the b-fix-db-subnet-refresh branch March 20, 2015 14:03
@dharmapunk82
Copy link

dharmapunk82 commented Aug 23, 2016

I'm hitting this on latest 0.7.1 running on ubuntu 14.04, for the eip_association resource. Lost network during a destroy then was not able to plan, apply, or taint the 2 resources in question.

I manually deleted the resources from tfstate and was then able to destroy the rest of the infrastructure, but wanted to report the bug... Plan and apply both failed with errors below prior to manually deleting them from tfstate:

Error refreshing state: 2 error(s) occurred:

  • aws_eip_association.ngomez_eip_assoc.1: Unable to find EIP Association: eipassoc-56135930
  • aws_eip_association.ngomez_eip_assoc.0: Unable to find EIP Association: eipassoc-fd13599b

Attempting to taint:
terraform taint eipassoc-56135930
Failed to parse resource name: Malformed resource state key: eipassoc-56135930

@ghost
Copy link

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

Successfully merging this pull request may close these issues.

refresh > resource not found (can?) create an error
3 participants