aws_emr_instance_group can't be destroyed

[synhershko]

Given a definition like below:

resource "aws_emr_instance_group" "querying-task-nodes" {
  name                      = "task"
  cluster_id                = "${aws_emr_cluster.querying.id}"
  instance_type             = "m4.xlarge"
  instance_count            = 5
}

If the EMR cluster is being destroyed successfully the instance group is getting into a limbo and can't be destroyed via terraform, giving the following error:

* aws_emr_instance_group.querying-task-nodes: ValidationException: An instance group may only be modified when the cluster is running or waiting.
	status code: 400, request id: d9555f4d-791e-11e7-b51e-cf8d28f27320

From what I can gather the issue is with the IG not being removed before the cluster is destroyed.

Using latest terraform (Terraform v0.10.0)

[timothyclifford]

Any updates?

We are seeing same behaviour with v0.11.2

[sbraden]

I recently observed this behavior on AWS. The work around (through the AWS Cloud Formation console) is when deleting the stack, opt to retain the resource (in this case the aws_emr_instance_group) that prevented the successful deletion of the stack. Then the delete of the stack can continue successfully.

[kutsav]

if the cluster with that task group is deleted, you can use terraform state rm to delete that entry from terraform state, and rerun your terraform to create cluster.

[bflad]

The fix for this has been merged and will release with version 2.32.0 of the Terraform AWS Provider, later today. Thanks to @joelthompson for the implementation. 🎉

[ghost]

This has been released in version 2.32.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 for triage. Thanks!

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