Pipeline never finishes deploying AWS ECS Fargate Task through codepipeline

Question

I set up a Fargate ecs service on AWS with multiple target groups and an application load balancer. It runs just as expected.

Then I tried to set up a pipeline using this tutorial

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-cd-pipeline.html

and now it is stuck at deployment stage and when I check out the deployments in ECS service. There's one ACTIVE and the other PRIMARY and I can visit both IPs. But the deployment never finishes and both will stay as my pipeline times out. Why is the ACTIVE one never going to drain in this case? Or is it because of the load balancer? I followed this tutorial with a service with single target group and the pipeline works as normal.

So I tried manually to stop ACTIVE task while deploy is still in progress. Now the pipeline finishes when I stop the ACTIVE task. So the question is how to change the settings so that ACTIVE task can be stopped automatically. — weitingtw, Apr 03 '20 at 12:37

score 1 · Answer 1 · answered Jan 05 '21 at 16:56

1

for me it was the:

minimum and maximum healthy percentage.

I changed it to 100 and 200 respectively. This worked for me...

answered Jan 05 '21 at 16:56

kumarahul

396
4
10

score 0 · Answer 2 · answered Apr 04 '20 at 15:20

From the description, I suspect your Tasks in PRIMARY group (the new task created as part of deployment) are not getting healthy on the ALB. During deployment, please check the Target groups to confirm the new tasks (by IPs) are healthy.

Once news tasks are healthy on ALB, ECS stops the old tasks / ACTIVE deployment.

Pipeline never finishes deploying AWS ECS Fargate Task through codepipeline

2 Answers2