-
Notifications
You must be signed in to change notification settings - Fork 3.4k
fix: Mark taskResult completed if wait container terminated not gracefully. Fixes #13373 #13491
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
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
@jswxstw Does this PR also address the scenario of a workflow with a step that gets OOMKilled and then retries and succeeds? |
@yonirab Can you provide your problem scenario(detail status of workflow and pod, logs of workflow-controller) in issue #13373? |
97f93d2 to
606f994
Compare
…inated not gracefully. Fixes argoproj#13373 Signed-off-by: oninowang <oninowang@tencent.com>
…fully. Fixes argoproj#13373 (argoproj#13491) Signed-off-by: oninowang <oninowang@tencent.com>
Fixes #13373
Motivation
#12103 (comment)
Modifications
Mark its taskResult as completed if pod has been terminated not gracefully.
Verification
This issue only occurs when
waitcontainer is terminated not gracefully, it is hard to reproduce it.kill -9wait/main containerErrorand wait container does not writeLabelKeyReportOutputsCompletedtotruecontroller log: