-
Notifications
You must be signed in to change notification settings - Fork 1
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
Track ECS container exit codes #2
Conversation
# Check if container's command returned error | ||
# or if ECS had an error running the command | ||
if 'exitCode' in container and container['exitCode'] != 0 \ | ||
or 'reason' in container: |
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.
i imagine that reasons
are not extraordinarily informative. but something's better than nothing - maybe we should let them bubble up?
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.
What do you mean by bubble up exactly?
I'm collecting all the failures into one exception and then raising that, as there might be multiple failing essential containers in one task, and ECS does not seem to kill all the tasks immediately on a failed essential container (there is some delay, and those containers that are subsequently terminated exit with exitCode
137), so multiple containers may have reason
/exitCode
set.
|
Do you have |
@codingmoose yessir - but i'll confirm |
Raise Exception to fail ECSTask if essential containers have non-zero exit codes.
The ECS test can be run with
tox -e py35 -- -x test/contrib/ecs_test.py
@p7k @bsusensjackson