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

provider/aws: Failing acceptance ECS tests - manual intervention #4568

Closed
radeksimko opened this issue Jan 8, 2016 · 3 comments
Closed

provider/aws: Failing acceptance ECS tests - manual intervention #4568

radeksimko opened this issue Jan 8, 2016 · 3 comments

Comments

@radeksimko
Copy link
Member

I don't know which one of @hashicorp/terraform can do this, I just wanted to give you heads up that the reason behind failing ECS acceptance tests in Travis is because there's a dangling ECS service & cluster. This should be just a leftover from a bug that was fixed last night by merging #4366 , specifically this line.

The way to fix this is to go to the AWS Console:
https://us-west-2.console.aws.amazon.com/ecs/home?region=us-west-2#/clusters/terraform-acc-test/services
and remove the service (tf-acc-ecs-svc) and then the cluster (terraform-acc-test) itself.

The next run should be green, unless the damn IAM gets in the way - something I'm trying to address in #4447

@phinze
Copy link
Contributor

phinze commented Jan 8, 2016

Thanks for the ping! Removed the colliding resources and re-kicked the build here:

https://travis-ci.org/hashicorp/terraform/jobs/100989751

Fingers crossed for good IAM juju 😉

@phinze
Copy link
Contributor

phinze commented Jan 8, 2016

Green! Thanks @radeksimko 😀

@phinze phinze closed this as completed Jan 8, 2016
@ghost
Copy link

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

2 participants