-
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
Workflow not Failed
despite having Error
node
#10994
Comments
Can you try v3.4.7? This might have been fixed already. |
Hi @terrytangyuan, thanks for the quick response. I updated the version in this issue, since I just reproduce this issue in v3.4.7. We only see this issue on Error node. For the Failed Node, argo workflow can always mark the workflow to Failed phase as long as any DAG Node Failed. |
Thanks. I am able to reproduce. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
Is there any updated? If no, could assign it to me? @agilgur5 |
Any updates would be in the issue. Please see https://sindresorhus.com/blog/issue-bumping & https://justinmayer.com/posts/any-updates/.
You don't need to be assigned to work on something, you can open a PR directly. |
Failed
despite having Error
node
https://github.com/argoproj/argo-workflows/blob/v3.6.0-rc4/workflow/controller/dag.go#L607 |
Pre-requisites
:latest
What happened/what you expected to happen?
What happened:
Workflow has
status.phase
Succeeded
, when when there is anError
node.What Expect:
Workflow
status.phase
should always beError
as long as there is anError
node.Version
v3.4.5 and v3.4.7
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.
Logs from the workflow controller
The text was updated successfully, but these errors were encountered: