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
Passing an output parameter from a template into a templateRef input argument fails with Bad Request: templates.main.steps[1].debug templates.debug: failed to resolve {{steps.generate-volume.outputs.parameters.pvc-name}}.
The supposedly invalid template used to work, and works when the templateRef is replaced with a template from the same file. It also worked briefly on retry when it initially stopped working (perhaps we were still running an old version of the web UI, if that is relevant), but on latest a workflow doesn't even get created before it fails.
I came across the same issue, it seems that if you remove prefix {{ and postfix }} in arguments value string, template is accepted and executed successfully.
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?
Passing an output parameter from a template into a templateRef input argument fails with
Bad Request: templates.main.steps[1].debug templates.debug: failed to resolve {{steps.generate-volume.outputs.parameters.pvc-name}}
.The supposedly invalid template used to work, and works when the templateRef is replaced with a template from the same file. It also worked briefly on retry when it initially stopped working (perhaps we were still running an old version of the web UI, if that is relevant), but on latest a workflow doesn't even get created before it fails.
Version(s)
86e51da260cf08708ef1debcb8af6bb373c93492635ce74c434f1012de58af08
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: