[X] 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.
[X] I have searched existing issues and could not find a match for this bug
I am running the latest stable release (3.5.11) of argo-workflows.
It seems a character escaping issue occurs during template rendering.
When feeding withParams or withItems with special characters, some wrong escaping occurs and container is called with wrong parameters, which is visible in the "inputs/outputs" tab of the side panel.
Depending on the input string, pods can be badly named in the graph view.
Parameters received by the debug pod:
(see the note below regarding the debug pod)
Moreover the displayed pod name does not share the same numerical identifier as the "ID". In this situation, the "Logs" button will not work. The logs are accessible from kubectl using the actual pod name (not being displayed).
Note: The provided custom image is intended for debugging this particular issue and can be built from this archive docker.zip using the following command: docker build -t localhost:5000/library/printarg:dev ..
As a workfaround, I managed to provide correct parameters to the python script using sprig to post-process the wrong escapes I encountered (double quote and backslashes). You can try calling the python script using param_workaround instead of param parameter.
Version(s)
v3.5.11
Paste a minimal 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?
Hi Argo.
I am running the latest stable release (3.5.11) of argo-workflows. It seems a character escaping issue occurs during template rendering.
When feeding withParams or withItems with special characters, some wrong escaping occurs and container is called with wrong parameters, which is visible in the "inputs/outputs" tab of the side panel. Depending on the input string, pods can be badly named in the graph view.
Parameters received by the debug pod: (see the note below regarding the debug pod)
Moreover the displayed pod name does not share the same numerical identifier as the "ID". In this situation, the "Logs" button will not work. The logs are accessible from kubectl using the actual pod name (not being displayed).
Note: The provided custom image is intended for debugging this particular issue and can be built from this archive docker.zip using the following command:
docker build -t localhost:5000/library/printarg:dev .
.As a workfaround, I managed to provide correct parameters to the python script using sprig to post-process the wrong escapes I encountered (double quote and backslashes). You can try calling the python script using
param_workaround
instead ofparam
parameter.Version(s)
v3.5.11
Paste a minimal 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