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

Error when running destroy for for terminated spot #1327

Closed
hashibot opened this issue Aug 3, 2017 · 4 comments · Fixed by #1903
Closed

Error when running destroy for for terminated spot #1327

hashibot opened this issue Aug 3, 2017 · 4 comments · Fixed by #1903
Labels
bug Addresses a defect in current functionality.

Comments

@hashibot
Copy link

hashibot commented Aug 3, 2017

This issue was originally opened by @eyalfishler as hashicorp/terraform#15699. It was migrated here as a result of the provider split. The original body of the issue is below.


v0.9.11
resource "aws_spot_instance_request" "player" {....

if the spot resource has been terminated by AWS and is no longer appearing in the AWS console as terminated (take a while) then you can not destroy the configuration.

terraform destroy
results in:
(same goes if u run plan)

Error refreshing state: 1 error(s) occurred:

  • aws_spot_instance_request.player: 2 error(s) occurred:

  • aws_spot_instance_request.player: aws_spot_instance_request.player: [ERR] Error reading Spot Instance Data: no instances found

  • aws_spot_instance_request.player[1]: aws_spot_instance_request.player.1: [ERR] Error reading Spot Instance Data: no instances found

@hashibot hashibot added the bug Addresses a defect in current functionality. label Aug 3, 2017
@Kentzo
Copy link

Kentzo commented Sep 11, 2017

Was the issue fixed?

@magnetik
Copy link

magnetik commented Oct 2, 2017

In the 0.1.1 provider it's not.

@Kentzo
Copy link

Kentzo commented Oct 4, 2017

Also happens with 1.0.0

Could anyone suggest a workaround?

@ghost
Copy link

ghost commented Apr 10, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants