-
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 succeeded with some node failed #6834
Comments
iven
added a commit
to iven/argo-workflows
that referenced
this issue
Oct 15, 2021
Signed-off-by: Iven Hsu <ivenvd@gmail.com>
alexec
pushed a commit
that referenced
this issue
Oct 18, 2021
kriti-sc
pushed a commit
to kriti-sc/argo-workflows
that referenced
this issue
Oct 24, 2021
Signed-off-by: Iven Hsu <ivenvd@gmail.com> Signed-off-by: kriti-sc <kathuriakriti1@gmail.com>
alexec
pushed a commit
that referenced
this issue
Nov 17, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
A workflow succeeded, but actually there's some nodes failed.
Reproduce on v3.1.6, v3.1.13, v3.2.0-rc4
Diagnostics
Currently all nodes organized like this. That's because we get TaskGroup's outbound nodes from their children, but A expand to nothing, it's an empty TaskGroup node, so it connects to TaskGroup B directly. So when C calls
connectDependencies
, it'll go throughA (TaskGroup) -> B (TaskGroup) -> B (DAG)
, and got nothing, because B (Pod) still Running, at this moment B (DAG) have no outbound node.Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: