-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
DAG outputs from task parameter don't work with a retry strategy #14228
Comments
Not the same. I ran the workflow you provided and it turned to I found that argo-workflows/workflow/controller/operator.go Lines 3273 to 3274 in b005487
The name of the child node has extra brackets and it panics here: argo-workflows/workflow/controller/operator.go Lines 3238 to 3252 in b005487
|
…#14228 Signed-off-by: oninowang <[email protected]>
…#14228 Signed-off-by: oninowang <[email protected]>
…#14228 Signed-off-by: oninowang <[email protected]>
…#14228 Signed-off-by: oninowang <[email protected]>
…#14228 Signed-off-by: oninowang <[email protected]>
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?
retryStrategy
on the Workflow spec, define a DAG with:withItems
, the template should have an output parametervalueFrom
Unable to resolve: "tasks.echo-list.outputs.parameters.dummy-output"
If you remove the
retryStrategy
from the spec, the DAG node succeeds first time and the workflow completes successfully. Note the problem also doesn't occur when usingsteps
.Looks like a similar root cause (retry strategy) as #13691
Further notes:
retryStrategy
set either in the workflow or the workflow controller configmapworkflowDefaults
retryStrategy
, there doesn't seem to be a way to removeretryStrategy
on the workflow, as argo will add the value from the configmap even if the workflow hasretryStrategy: {}
retryStrategy: {}
will break the workflow (even if it's not set in the config map)Version(s)
v3.6.4
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow 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: