-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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: ensure that nodes complete when workflow fails with parallelism
and failFast
. Fixes #13806
#13827
Conversation
parallelism
and failFast
. Fixes #13806
@agilgur5 Not yet, but #10312 is not related to this issue,
|
…and failFast enabled. Fixes argoproj#13806 Signed-off-by: oninowang <[email protected]>
We usually set global workflow-level parallelism to limit resource usage, so once the workflow enables |
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.
Looks good. I ran both examples from #13806 and verified both correctly failed with this fix:
$ ./dist/argo list -o wide
NAME STATUS AGE DURATION PRIORITY MESSAGE P/R/C PARAMETERS
dag-4rrxm Failed 55s 37s 0 template has failed or errored children and failFast enabled 0/0/2
steps-gnh5p Failed 1m 41s 0 template has failed or errored children and failFast enabled 0/0/2
@terrytangyuan @Joibel @isubasinghe Could you please take some time to review this PR? Thank you very much! |
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.
LGTM. Thanks!
…` and `failFast`. Fixes argoproj#13806 (argoproj#13827)
…` and `failFast`. Fixes argoproj#13806 (argoproj#13827)
Fixes #13806
Motivation
The
FailFast
feature has two serious flaws:Steps
node as Failed, the lastStepGroup
node is still Running.Modifications
StepGroup
node asFailed
.Verification
local test and e2e tests
Test workflow: