-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix (ecs): Unstable deployments for task definitions with more than one container (#5544) #4409
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add unit tests to verify that tasks with network bindings in containers other than the first one are correctly evaluated?
Normally, that's the first thing I do when introducing a change, but I was quite in a hurry with the fix for my own purposes and I also need to figure out how these particular unit tests work. |
…r in task definition (spinnaker#5544)
quoting @atyutyunnik from the slack convo about this issue:
🎉 |
@spinnakerbot cherry-pick 1.19 |
Cherry pick successful: #4416 |
…r in task definition (#5544) (#4409) (#4416) Co-authored-by: Alexander Tyutyunnik <alexandert@edifecs.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: atyutyunnik <45210095+atyutyunnik@users.noreply.github.com> Co-authored-by: Alexander Tyutyunnik <alexandert@edifecs.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
@spinnakerbot cherry-pick 1.18 |
Cherry pick failed: Command failed (cherry pick commit 2a7ad04) with exit code 1:
|
For 1.18, you have to use PR# 4411. PR4409 is not compatible with the code base |
The original code will not finish deployment and will eventually time out, in spite of task being successfully deployed by ECS and running (spinnaker/spinnaker#5544)