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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClientException: Too many concurrent attempts to create a new revision of the specified family. #9777
Comments
I'm running into the same issue. I reduced the Terraform configuration to make it easier to reproduce it (the left out facts are the same as in the initial post): Terraform VersionTerraform v0.12.7 Terraform Configuration Filesresource "aws_ecs_task_definition" "this" {
count = 2
family = "test-family"
container_definitions = jsonencode([{
name = "test"
image = "dummy"
memory = 512
}])
} Important FactoidsThe error can be circumvented by running When you set |
I had similar issue. I was able to fix it by using different family for each task definition. |
You should have two task definitions with different values for family. One for the frontend, one for the backend.
Task definition has nothing to do with your cluster, you can use the same in many clusters, or on many services. But if each service runs a different set of containers, that's a different task definition. |
still an issue 2 years later lol for terragrunt, use: |
Hey y'all 馃憢 Thank you for taking the time to file this issue and for the continued discussion! Given that there's been a number of AWS provider releases since this was initially filed (and since the last update), can anyone confirm whether you're still experiencing this behavior? |
I've just seen this issue when deploying via Terraform Cloud :( |
Yes, I'm also still seeing this. Just hit it now actually which brought me here. I have a root module that deploys 2 target groups of tasks with different versions of the same task family so we can switch back and forth via the load balancer if needed for a blue/green style deployment. Whenever there is a change to our terraform code and both container groups are active we run into this issue. |
Still an issue, ran into it today with provider 4.1 |
Still an issue with |
Still running into this issue with creating 1 ECS cluster. Running the apply back to back usually gets over it. |
Still an issue when using |
Yep, still receiving this issue as well with TF 1.2.9 and the latest aws provider. Just have to re-run the apply to fix it. |
Same for me. The only solution would be to create many families like proposed on other comments |
Still a problem on provider v4.32.0 |
Same issue for for me as well. |
Encountered this problem today as well while applying just three containers sharing the same family into a single cluster. Had to give each of them unique family IDs to circumvent which, admittadly, is not a terrible workaround. Edit: Appending an incremental integer to each family name did not work for me. Hm... |
Community Note
Terraform Version
Terraform v0.12.5
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Running
terraform apply
again and again should not cause any errors. I expect that AWS task definitions get updated properly.Actual Behavior
AWS task definitions don't get updated and an error is thrown approximately 1 out of 5 attempts. If I rerun
terraform apply
another time, it usually works.Steps to Reproduce
terraform apply
Important Factoids
Nothing special. Just two ECS services and the corresponding task definitions for them. It's worth noting that they are both within the same "family". Maybe this has some impact?
The text was updated successfully, but these errors were encountered: