This is probably https://github.com/ovn-org/ovn-kubernetes/pull/1139 (fixed upstream but not merged into our builds yet).
@Dan, So PR 1139 is trying to make level 5 as default. Aren't we supposed to stay at level 4(INFO) by default?
And apparently without this PR even, currently i see logs at level 5 but config set to 4.
The title of the PR is confusing... I don't really understand what it's supposed to be saying.
The problem is that we intentionally bump the log level up to 5 at startup time so that if something goes wrong we'll have sufficient logs about it. It's *supposed* to set the log level back down to the configured level after startup is complete, but that was broken. That's what the PR fixes.
Make sense to me now @Dan. Thanks for clarifications.
I doubt that this bug is related to: https://github.com/ovn-org/ovn-kubernetes/pull/1139, that PR fixes an issue with ovnkube when klog was already activated. The logs Anurag attached show logrus still being used...
I think this problem is something that might have impacted ovnkube when logrus was activated, or something that might come to impact klog too. It's really strange that the log-level is not respected.
Verified log level 4 (INFO) on 4.4.0-0.nightly-2020-04-15-071550
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.