Skip to content
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

3.6.2 CLI: Do not print help output on submission error #14234

Open
4 tasks done
jumpe1 opened this issue Feb 28, 2025 · 0 comments · May be fixed by #14235
Open
4 tasks done

3.6.2 CLI: Do not print help output on submission error #14234

jumpe1 opened this issue Feb 28, 2025 · 0 comments · May be fixed by #14235
Labels

Comments

@jumpe1
Copy link

jumpe1 commented Feb 28, 2025

Pre-requisites

  • I have double-checked my configuration
  • 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
  • I'd like to contribute the fix myself (see contributing guide)

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

Not relevant to this issue.

Logs from in your workflow's wait container

Not relevant to this issue.
jumpe1 added a commit to jumpe1/argo-workflows that referenced this issue Feb 28, 2025
jumpe1 added a commit to jumpe1/argo-workflows that referenced this issue Feb 28, 2025
@jumpe1 jumpe1 linked a pull request Feb 28, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant