You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested with the :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.
I have searched existing issues and could not find a match for this bug
The dag dependencies are quite complicated. (40+ nodes and several nodes have more than 5 dependencies)
Each dag node is a container set.
Each container set has a simple DAG. (prepare-inputs -> main -> prepare-outputs)
The workflow below failed every time. When I changed the inner dag from containers to dag or step groups, it would succeed.
Expectation: Container sets works well as dag/step groups when it is used as node nested in the complex workflow. What happened:
The workflows failed with error info below.
&{0x3a297a0 map[namespace:pipeline workflow:pipeline-test-point-simplefied-g5gbq] 2024-04-30 03:46:14.425189512 +0000 UTC m=+158960.631405283 panic <nil> was unable to obtain node for pipeline-test-point-simplefied-g5gbq-2664608158 <nil><nil> }
The DAG showed in GUI was wrong with an invalid dependencies tree. For example, I and J has the same dependencies but they were connected as if J depended on I, as below.
So far as I tested, DAGs showed in the Argo GUI were wrong even for some very simple container set. I suspected that if the crash were some how connected to such wrong DAG behavior.
Version
latest (3.5.6)
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.
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?
A complex workflow has below structure.
The workflow below failed every time. When I changed the inner dag from containers to dag or step groups, it would succeed.
Expectation: Container sets works well as dag/step groups when it is used as node nested in the complex workflow.
What happened:
I
andJ
has the same dependencies but they were connected as ifJ
depended onI
, as below.Version
latest (3.5.6)
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
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: