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

Terraform Crash #3879

Closed
hutchic opened this issue Nov 12, 2015 · 5 comments
Closed

Terraform Crash #3879

hutchic opened this issue Nov 12, 2015 · 5 comments

Comments

@hutchic
Copy link

hutchic commented Nov 12, 2015

Terraform plan crashed and in the crash notes it asked me to create an issue so here I am :)

crash.txt

@hutchic
Copy link
Author

hutchic commented Nov 12, 2015

re-exported my AWS credentials and now it's happy

@jen20
Copy link
Contributor

jen20 commented Nov 12, 2015

HI @hutchic! Thanks for reporting the issue. Looking through your logs, a crash like that is definitely a bug. Is there a possibility you had AWS credentials in your environment for another AWS account which did not have any ECS clusters?

@hutchic
Copy link
Author

hutchic commented Nov 13, 2015

That's definitely a possibility

@radeksimko
Copy link
Member

Interesting part of the crash log:

2015/11/12 08:45:05 terraform-provider-aws: 2015/11/12 08:45:05 [DEBUG] Received ECS clusters: []
2015/11/12 08:45:05 terraform-provider-aws: panic: runtime error: index out of range
2015/11/12 08:45:05 terraform-provider-aws: 
2015/11/12 08:45:05 terraform-provider-aws: goroutine 47 [running]:
2015/11/12 08:45:05 terraform-provider-aws: github.com/hashicorp/terraform/builtin/providers/aws.resourceAwsEcsClusterRead(0xc208063500, 0x6befe0, 0xc20806c360, 0x0, 0x0)
2015/11/12 08:45:05 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

I'm going to close this as this exact bug was fixed a few days ago via #3829 and will be part of the next release.

Thank you for the report @hutchic though.

@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

No branches or pull requests

3 participants