Bug 1746942

Summary: spec.logLevel on openshiftapiservers/cluster has no effect on openshift-apiserver logging
Product: OpenShift Container Platform Reporter: Oleg Bulatov <obulatov>
Component: openshift-apiserverAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, mfojtik, rkratky
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:38:33 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:

Description Oleg Bulatov 2019-08-29 14:42:16 UTC
Version-Release number of selected component (if applicable):

4.2.0-0.okd-2019-08-28-145113

Steps to Reproduce:
1. oc edit openshiftapiservers/cluster
2. change logLevel to Trace
3. wait a minute until the daemonset gets updated
4. check logs from openshift-apiserver pods: for pod in $(oc -n openshift-apiserver get pods -o jsonpath='{range .items[*]}{.metadata.name}{"\n"}{end}'); do oc -n openshift-apiserver logs "$pod"; done

Expected results:

There should be lines from klog.V(5), like this:

I0829 14:38:13.068419       1 pathrecorder.go:240] apps.openshift.io-apiserver: "/openapi/v2" satisfied by exact match

Additional info:

Comment 2 Xingxing Xia 2019-09-10 00:26:22 UTC
Verified in 4.2.0-0.nightly-2019-09-08-180038

Comment 3 errata-xmlrpc 2019-10-16 06:38:33 UTC
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/RHBA-2019:2922