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 refreshing EMR Instance Group when EMR Cluster no longer exists #19552

Closed
adam-tylr opened this issue May 27, 2021 · 2 comments · Fixed by #26154
Closed

Error refreshing EMR Instance Group when EMR Cluster no longer exists #19552

adam-tylr opened this issue May 27, 2021 · 2 comments · Fixed by #26154
Labels
bug Addresses a defect in current functionality. service/emr Issues and PRs that pertain to the emr service.
Milestone

Comments

@adam-tylr
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.13.6
AWS Provider 3.39.0

Affected Resource(s)

  • aws_emr_instance_group

Terraform Configuration Files

I do not have any as I'm only trying to destroy state containing clusters that were long ago deleted

Debug Output

Error: error reading EMR Instance Group (ig-...): unable to retrieve EMR Cluster ("j-..."): InvalidRequestException: Cluster id 'j-...' is not valid.
{
  RespMetadata: {
    StatusCode: 400,
    RequestID: "..."
  },
  ErrorCode: "NoSuchCluster",
  Message_: "Cluster id 'j-...' is not valid."
}

Panic Output

Expected Behavior

Terraform should detect the resource no longer exists and remove it from state during the refresh

Actual Behavior

Terraform exits

Steps to Reproduce

  1. Deploy an EMR cluster + instance group
  2. Delete them manually
  3. run terraform destroy

References

The fix is the same as #16924 except on the instance group resource instead of the cluster. I will open a PR

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/emr Issues and PRs that pertain to the emr service. labels May 27, 2021
@ewbankkit ewbankkit added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 2, 2021
@github-actions github-actions bot added this to the v4.26.0 milestone Aug 8, 2022
@github-actions
Copy link

This functionality has been released in v4.26.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 12, 2022
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. service/emr Issues and PRs that pertain to the emr service.
Projects
None yet
2 participants