-
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
failFast
field doesn't work
#10312
Comments
@sarabala1979 I would be happy to see if I can find the issue. |
@NikeNano Thanks Nike. Please submit the PR |
@sarabala1979 Could you clarify what is the status of the I'm asking because it doesn't seem to work on our side either, and I found clues in past GH issues (although quite old) that there are known bugs that wouldn't be fixed in favour to a different feature. |
I encountered the same issue. Does this issue has been fixed? Is there any one can help me, thx. |
@aaaaahaaaaa @dablelv Would you like to submit the fix? we are happy to have more contributors |
Thank you for your invitation. If I have free time, I‘m very happy to join the work of Argo. Besides, I found a way to solve this issue temporarily in the biz code. If one node of the workflow failed, the workflow PHASE became "Failed". So we can let a node to poll the current workflow state to stop itself. It's not elegant, but it can solve the problem. |
affecting 3.4.7 version also |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
hi @agilgur5 please assign me. I have found the location where the bug occurred, but I have found that this modification will affect some execution and node status of the entire DAG workflow, so I have a question about this fix So do we need to mark the unscheduled pods as |
Mentioned on Slack that you can submit a PR directly, no need to be assigned. Regarding unscheduled nodes, good question, I believe they should be marked as "Skipped". When a Workflow is shutdown (terminated or stopped), all unscheduled nodes are currently marked as "Skipped", so that would match that existing behavior. |
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Signed-off-by: Goober <chenhao86899@gmail.com>
Pre-requisites
:latest
What happened/what you expected to happen?
failFast flag is invalid
Version
v3.4.2
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
The dependencies are as follows :
When I was using FailFast, I found that this parameter was invalid. Regardless of setting True/False, step C failed, and BDE would execute it.
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: