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
In previous versions of cmd/argoexec (< 3.6), when a workflow submission failed, only the error message was output.
Currently, I am using v3.6.2, and in case of a failure, the entire help message is printed along with the error message. This results in a lot of unnecessary log output, which adds noise and makes it inconvenient to check the actual error.
A similar issue has already been reported in the following issue.
However, that issue only addressed the cmd/argo side. It seems that cmd/argoexec also needs to be addressed in the same way.
Version(s)
v3.6.2
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.
argo submit 'ANYexampleworkflow.yaml'
Logs from the workflow controller
Not relevant to this issue.
Logs from in your workflow's wait container
Not relevant to this issue.
The text was updated successfully, but these errors were encountered:
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?
In previous versions of cmd/argoexec (< 3.6), when a workflow submission failed, only the error message was output.
Currently, I am using v3.6.2, and in case of a failure, the entire help message is printed along with the error message. This results in a lot of unnecessary log output, which adds noise and makes it inconvenient to check the actual error.
A similar issue has already been reported in the following issue.
However, that issue only addressed the cmd/argo side. It seems that cmd/argoexec also needs to be addressed in the same way.
Version(s)
v3.6.2
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.
argo submit 'ANYexampleworkflow.yaml'
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: