Skip to content

Fix deployment rollbacking with more than 100 tasks#176

Open
adrien-f wants to merge 2 commits into
fabfuel:developfrom
adrien-f:paginate-tasks
Open

Fix deployment rollbacking with more than 100 tasks#176
adrien-f wants to merge 2 commits into
fabfuel:developfrom
adrien-f:paginate-tasks

Conversation

@adrien-f
Copy link
Copy Markdown

@adrien-f adrien-f commented Jul 19, 2021

The list_tasks call was capped at 100 tasks, if the service had a desired
superior of 100 the deployment would fail.

Fix #174

Signed-off-by: Adrien Fillon adrien.fillon@manomano.com

@adrien-f
Copy link
Copy Markdown
Author

adrien-f commented Jul 19, 2021

I'm still doing more tests so do not merge 🙏 I forgot to open it as draft, my bad

We've tested a deployment with more than 100 tasks and it went through this time!

The `list_tasks` call was capped at 100 tasks, if your service had a desired
superior of 100 the deployment would fail.

Fix fabfuel#174

Signed-off-by: Adrien Fillon <adrien.fillon@manomano.com>
@joshmyers
Copy link
Copy Markdown

Yeah, this doesn't work if >100 tasks. Deployment times out despite having completed on the ECS side. Any chance of this getting merged?

@zgilkerson
Copy link
Copy Markdown

We ran into a similar issue this past week regarding timeouts when more than 100 tasks were running. This PR looks like it solves the issue in a way more inline with the existing code base while the strategy that my team took was to ignore counting tasks altogether by checking has_completed on the primary deployment
Screenshot 2023-03-10 at 10 45 28

0001-utilize-has_completed-for-is_deployed-check.patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can the desired target change during deployments?

4 participants