-
Notifications
You must be signed in to change notification settings - Fork 617
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
taskresources: ensure terminal reason messages are applied in all known failure paths #1631
Comments
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
Apr 25, 2019
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
Apr 26, 2019
closes aws#1631 return a default terminal reason remove terminalReason code for cgroups based on PR review Test that volume errors are propogated
sparrc
added a commit
to sparrc/amazon-ecs-agent
that referenced
this issue
Apr 29, 2019
closes aws#1631 return a default terminal reason remove terminalReason code for cgroups based on PR review Test that volume errors are propogated
sparrc
added a commit
that referenced
this issue
Apr 29, 2019
* taskresources: set terminal reason msg for all errors closes #1631 return a default terminal reason remove terminalReason code for cgroups based on PR review Test that volume errors are propogated * fix cleanup error test and add string check
fierlion
added a commit
to fierlion/amazon-ecs-agent
that referenced
this issue
Apr 30, 2019
Updating to go 1.12 Make CGroups CPU period configurable Signed-off-by: Mohamad Arab <[email protected]> taskresources: set terminal reason msg for all errors (aws#2004) * taskresources: set terminal reason msg for all errors closes aws#1631 return a default terminal reason remove terminalReason code for cgroups based on PR review Test that volume errors are propogated * fix cleanup error test and add string check Fix telemetry test for ws2019 On WS2019 functional test image mcr.microsoft.com/windows/servercore:ltsc2019, the behavior to handle path changed from ws2016 image, it needs to set entrypoint with absolute path or have entrypoint set to powershell to run executable without absolute path. Also removed unused binary in windows telemetry test. add storageReadBytes storageWriteBytes stats
fierlion
pushed a commit
to fierlion/amazon-ecs-agent
that referenced
this issue
Apr 30, 2019
* taskresources: set terminal reason msg for all errors closes aws#1631 return a default terminal reason remove terminalReason code for cgroups based on PR review Test that volume errors are propogated * fix cleanup error test and add string check
closed by #2004 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
For task resource cgroup and volume, the terminal reason attributes need to to added to the model and when it has errors, the error message needs to be populated into the terminal reason. So the terminal reason can be communicated to service side and show to customers.
Expected Behavior
As what ASMAuthResource is doing nowadays, there is a terminal reason attribute in the model, and every time when resource logic has errors, this attribute will be populated with the error message. Later on, it will be used as task stop reason and customers are able to see it.
Observed Behavior
So far, cgroup and volume do not have this attribute, so the error message cannot be communicated back to customers.
The text was updated successfully, but these errors were encountered: