Bug 1484095
| Summary: | REST request log spam is back in OCP 3.7 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | |
| Component: | Node | Assignee: | Avesh Agarwal <avagarwa> | |
| Status: | CLOSED ERRATA | QA Contact: | Mike Fiedler <mifiedle> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.7.0 | CC: | aos-bugs, eparis, erich, jokerman, mifiedle, mmccomas, sjenning, xtian | |
| Target Milestone: | --- | |||
| Target Release: | 3.7.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1531557 1531558 (view as bug list) | Environment: | ||
| Last Closed: | 2017-11-28 22:07:41 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1531557, 1531558 | |||
|
Description
Mike Fiedler
2017-08-22 16:50:22 UTC
Avesh, this is a 3.7 regression of bz1414813. Can you create a pick for origin master? Also, we need to get the upstream PR merged so this doesn't happen on every rebase https://github.com/kubernetes/kubernetes/pull/40933 (In reply to Seth Jennings from comment #1) > Avesh, this is a 3.7 regression of bz1414813. Can you create a pick for > origin master? Ok I will create it soon. > > Also, we need to get the upstream PR merged so this doesn't happen on every > rebase https://github.com/kubernetes/kubernetes/pull/40933 Please help and put your weight in the PR, any help to support that PR is more than welcome. Mike, is it acceptable for you to decrease the overall loglevel to 1 and use --logspec to selectively increase the log level on a per package basis? Almost every problem we (QE) provide logs for, dev wants at least loglevel 2. The types of problems we find in scalability and performance testing are often difficult or impossible to recreate and the first failure logs are critical to debugging. I think having online, customers and QE run at loglevel 1 is going to result in a lot of frustration for support and development. ping @eparis and @erich Another option here is to just carry the patch. That PR is already open: https://github.com/openshift/origin/pull/15934 Just need to agree to the carry and inform deads to let the PR through. Both Erics, what do you think? (In reply to Mike Fiedler from comment #6) > Almost every problem we (QE) provide logs for, dev wants at least loglevel > 2. The types of problems we find in scalability and performance testing are > often difficult or impossible to recreate and the first failure logs are > critical to debugging. I think having online, customers and QE run at > loglevel 1 is going to result in a lot of frustration for support and > development. > > ping @eparis and @erich The plan is to continue with loglevel to default to 2 and only for that file (http log) is to have at level 1 by using logspec. So it'd look like this: --loglevel=2 --logspec='httplog=1' +1 to comment 9 if it works Online/RH managed clusters run at v2. I can't speak for QE clusters... I don't care if it is a CARRY. These calls need to be gone by default in V(2) in openshift. Moved to post as the carry is already open https://github.com/openshift/origin/pull/15934 Eric just approved it. Verified on 3.7.0-0.127.0. Logs are usable again ;-) 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. https://access.redhat.com/errata/RHSA-2017:3188 |