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

ECS wait services-stable returns prematurely when leveraging --force-new-deployment rollout #9275

Open
1 task
ohshazbot opened this issue Feb 4, 2025 · 1 comment
Assignees
Labels
bug This issue is a bug. ecs p2 This is a standard priority issue service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@ohshazbot
Copy link

Describe the bug

When deploying leveraging --force-new-deployment to reuse existing task definition and then attempting to use ecs wait services-stable results in the wait returning before the rollout of the new software versions completes.

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

I would expect ecs wait services-stable to wait until the deployment completes (or times out) before returning

Current Behavior

ecs wait services-stable returns after a subset of instances are updated, resulting in the operation completing while a mix of old and new versions are operational

Reproduction Steps

aws ecs update-service --cluster ${ECS_CLUSTER} --service ${SERVICE_NAME} --force-new-deployment
aws ecs wait services-stable --cluster ${ECS_CLUSTER} --services ${SERVICE_NAME}

And observe (quickly) that the service is still mid-deployment

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.18.4

Environment details (OS name and version, etc.)

Python/3.12.7 Linux/6.8.0-51-generic source/x86_64.ubuntu.24

@ohshazbot ohshazbot added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 4, 2025
@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Feb 12, 2025
@RyanFitzSimmonsAK RyanFitzSimmonsAK added investigating This issue is being investigated and/or work is in progress to resolve the issue. ecs p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Feb 12, 2025
@RyanFitzSimmonsAK
Copy link
Contributor

Hi @ohshazbot, thanks for reaching out. This looks like a service issue rather than an SDK issue, and I did find similar reports of inconsistent behavior with this waiter. I've reached out to the ECS service team about this issue. I'll let you know when I have any updates.

Ticket # for internal use : P203308568

@RyanFitzSimmonsAK RyanFitzSimmonsAK added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. service-api This issue is due to a problem in a service API, not the SDK implementation. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. ecs p2 This is a standard priority issue service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants