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

"Re-establishing workflow watch" should be debug-level #2955

Closed
4 tasks done
samath117 opened this issue May 5, 2020 · 0 comments · Fixed by #2958
Closed
4 tasks done

"Re-establishing workflow watch" should be debug-level #2955

samath117 opened this issue May 5, 2020 · 0 comments · Fixed by #2958
Labels

Comments

@samath117
Copy link

Checklist:

  • I've included the version.
  • I've included reproduction steps.
  • I've included the workflow YAML.
  • I've included the logs.

What happened:

When running argo logs -f on any workflow that runs for long enough, the logs are sprinkled with lines that start like this:

INFO[0068] Re-establishing workflow watch

(The namespace and workflow name are also listed after several spaces.) These logs are usually only present when invoking a higher --loglevel, like debug (this is using the default, info). This appears to be a mistaken byproduct of a fix to #2796.

What you expected to happen:

Those logs should be on the debug level, not the info level.

How to reproduce it (as minimally and precisely as possible):

Run the workflow in #2796 and then run argo logs -f on the result. A line like the above will appear after a bit over a minute.

This is in Argo v2.7.6, which has the fix to #2796.


Message from the maintainers:

If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

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