You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
locked and limited conversation to collaborators
Apr 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: