-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
node stuck Running
when Parallelism
and FailFast
is enabled during parallel execution
#13806
Closed
4 tasks done
Labels
area/controller
Controller issues, panics
area/parallelism
`parallelism` for the Controller, Workflows, or templates
type/bug
type/regression
Regression from previous behavior (a specific type of bug)
Comments
jswxstw
added
type/bug
area/controller
Controller issues, panics
area/looping
`withParams`, `withItems`, and `withSequence`
area/parallelism
`parallelism` for the Controller, Workflows, or templates
and removed
area/looping
`withParams`, `withItems`, and `withSequence`
labels
Oct 24, 2024
jswxstw
changed the title
Oct 25, 2024
StepGroup
node stuck Running
when looping with FailFast
StepGroup
node stuck Running
when using template-level parallelism
and FailFast
jswxstw
changed the title
node stuck Oct 25, 2024
StepGroup
node stuck Running
when using template-level parallelism
and FailFast
Running
when FailFast
is enabled during parallel execution
jswxstw
changed the title
node stuck
node stuck Oct 25, 2024
Running
when FailFast
is enabled during parallel executionRunning
when Parallelism
and FailFast
is enabled during parallel execution
jswxstw
added a commit
to jswxstw/argo-workflows
that referenced
this issue
Oct 28, 2024
…and failFast enabled. Fixes argoproj#13806 Signed-off-by: oninowang <oninowang@tencent.com>
jswxstw
added a commit
to jswxstw/argo-workflows
that referenced
this issue
Oct 31, 2024
…and failFast enabled. Fixes argoproj#13806 Signed-off-by: oninowang <oninowang@tencent.com>
Also, the pod of node |
jswxstw
added
the
type/regression
Regression from previous behavior (a specific type of bug)
label
Dec 11, 2024
This issue was introduced by feature #5315. |
isubasinghe
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jan 30, 2025
…` and `failFast`. Fixes argoproj#13806 (argoproj#13827)
isubasinghe
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jan 31, 2025
…` and `failFast`. Fixes argoproj#13806 (argoproj#13827)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/controller
Controller issues, panics
area/parallelism
`parallelism` for the Controller, Workflows, or templates
type/bug
type/regression
Regression from previous behavior (a specific type of bug)
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
Case 1: parallel steps with failFast
Case 2: parallel tasks with failFast
The official example can reproduce this issue as well.
These issues are all introduced by
checkParallelism
, some scenarios have not been taken into account.The
FailFast
feature has two serious flaws:Steps
node asFailed
, the lastStepGroup
node is stillRunning
.argo-workflows/workflow/controller/operator.go
Lines 2781 to 2785 in 2cc6b32
Version(s)
2cc6b32
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Case 1: parallel steps with failFast
Case 2: parallel tasks with failFast
Logs from the workflow controller
Case 1: parallel steps with failFast
Case 2: parallel tasks with failFast
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: