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.

Sign up for GitHub

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

Jump to bottom

There is always a DEBUG-level log in the router log #2768

Open
saltbo opened this issue Apr 4, 2023 · 1 comment · May be fixed by #2769
Open

There is always a DEBUG-level log in the router log #2768

saltbo opened this issue Apr 4, 2023 · 1 comment · May be fixed by #2769
Labels
bug

Comments

@saltbo
Copy link
Contributor

saltbo commented Apr 4, 2023

Fission/Kubernetes version

$ fission version
$ kubectl version

Kubernetes platform (e.g. Google Kubernetes Engine)

Describe the bug

There is always a DEBUG-level log in the router log even the DEBUG_ENV=false:

2023/04/04 05:42:27 [DEBUG] POST http://executor.fission-system/v2/getServiceForFunction
2023/04/04 05:42:28 [DEBUG] POST http://executor.fission-system/v2/unTapService

To Reproduce

DEBUG_ENV=false

kubectl logs -n fission-system deployment/router

Expected result

No debug log

Actual result
Always show a debug log

Screenshots/Dump file

$ fission support dump

Additional context
@saltbo saltbo linked a pull request Apr 4, 2023 that will close this issue
Open
5 tasks
@NikhilSharmaWe
Copy link
Member

@sanketsudake Could you please take a look at this issue and let us know whether this is a reasonable bug or not? So, @saltbo can continue to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: set leveledlogger for the pkg retryablehttp saltbo/fission
2 participants
@saltbo @NikhilSharmaWe