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

Crash in aws_ecs_cluster read with missing ECS cluster #3826

Closed
jlafleche opened this issue Nov 9, 2015 · 3 comments · Fixed by #3829
Closed

Crash in aws_ecs_cluster read with missing ECS cluster #3826

jlafleche opened this issue Nov 9, 2015 · 3 comments · Fixed by #3829

Comments

@jlafleche
Copy link

Edit by @catsby: extracted crash log to https://gist.github.com/catsby/936ee356cff32b12eb5b

Key bit:

terraform-provider-aws: 2015/11/09 10:56:07 [DEBUG] Received ECS clusters: []
terraform-provider-aws: panic: runtime error: index out of range
terraform-provider-aws: 
terraform-provider-aws: goroutine 42 [running]:
terraform-provider-aws: github.com/hashicorp/terraform/builtin/providers/aws.resourceAwsEcsClusterRead(0xc2083750e0, 0x6befe0, 0xc20805a360, 0x0, 0x0)
terraform-provider-aws:     /private/tmp/terraform20150812-1536-1wacuhp/terraform-0.6.3/src/github.com/hashicorp/terraform/builtin/providers/aws/resource_aws_ecs_cluster.go:62 +0x55f
terraform-provider-aws: github.com/hashicorp/terraform/helper/schema.(*Resource).Refresh(0xc2081772c0, 0xc20836bd40, 0x6befe0, 0xc20805a360, 0xc20806b2f0, 0x0, 0x0)
@jlafleche
Copy link
Author

Context on the crash:

I had a partially applied terraform state - I then changed the AWS region and re-applied, and hit the crash.

@catsby
Copy link
Contributor

catsby commented Nov 9, 2015

Thanks @jlafleche – I've patched this in #3829

@apparentlymart apparentlymart changed the title Terraform Crash Crash in aws_ecs_cluster read with missing ECS cluster Nov 10, 2015
omeid pushed a commit to omeid/terraform that referenced this issue Mar 30, 2018
…ch_configuration-randomize

tests/resource/aws_launch_configuration: Standardize and randomize names
@ghost
Copy link

ghost commented Apr 30, 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 30, 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