Bug 1791888 - apiserver cannot handle logLevel and operatorLogLevel
Summary: apiserver cannot handle logLevel and operatorLogLevel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.2.z
Hardware: x86_64
OS: All
high
low
Target Milestone: ---
: 4.2.z
Assignee: Vikram Goyal
QA Contact: Xingxing Xia
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-16 16:35 UTC by Arnab Ghosh
Modified: 2024-01-06 04:27 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-02 11:02:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0936 0 None None None 2020-04-02 11:02:49 UTC

Description Arnab Ghosh 2020-01-16 16:35:05 UTC
Document URL: 
[1] - https://docs.openshift.com/container-platform/4.2/nodes/nodes/nodes-nodes-audit-log.html#nodes-nodes-audit-log-basic-config_nodes-nodes-audit-log

Section Number and Name: 

Describe the issue: 
configuring log levels in APIServer resource as per [1] is a document bug as it does not at all change log levels for API. In CRD definition we could see that it is for kubeapiserver and openshiftapiserver.

~~~
$ oc explain apiserver.spec | grep -i loglevel 
$ 
$ oc explain kubeapiserver.spec | grep -i loglevel 
   logLevel     <string>
     logLevel is an intent based logging for an overall component. It does not
   operatorLogLevel     <string>
     operatorLogLevel is an intent based logging for the operator itself. It
$ 
$ oc explain openshiftapiserver.spec | grep -i loglevel 
   logLevel     <string>
     logLevel is an intent based logging for an overall component. It does not
   operatorLogLevel     <string>
     operatorLogLevel is an intent based logging for the operator itself. It
$ 
~~~

Suggestions for improvement: 

Documentation should reflect properly

Additional information:

Comment 1 Michael Burke 2020-02-13 16:05:36 UTC
Arnab --

Thank you for filing this BZ. Is the request to remove the "Configuring the API Audit Log level" [1] from the docs until the RFE mentioned in the customer case is implemented?

If so, please see: Docs PR: https://github.com/openshift/openshift-docs/pull/19721
Preview available at: https://bz-1791888--ocpdocs.netlify.com/openshift-enterprise/latest/nodes/nodes/nodes-nodes-audit-log.html

Michael

[1] https://docs.openshift.com/container-platform/4.2/nodes/nodes/nodes-nodes-audit-log.html#nodes-nodes-audit-log-basic-config_nodes-nodes-audit-log

Comment 2 Arnab Ghosh 2020-02-14 09:48:33 UTC
Hi Mike,

Mike: Is the request to remove the "Configuring the API Audit Log level" [1] from the docs until the RFE mentioned in the customer case is implemented?
Arnab: Yes, the RFE is not assigned yet.

Mike: If so, please see: Docs PR: https://github.com/openshift/openshift-docs/pull/19721
Arnab: I see you have removed 'Configuring the API Audit Log level'. However I was expecting this part of the document to be modified with correct steps required to perform the same.

Regards
Arnab

Comment 13 Xingxing Xia 2020-03-23 11:32:10 UTC
Moving this bug to VERIFIED due to the doc PR LGTM.

Comment 14 Xingxing Xia 2020-03-23 11:37:20 UTC
Using bug 1816115 to separately check another topic of this bug.

Comment 18 errata-xmlrpc 2020-04-02 11:02:40 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-2020:0936

Comment 21 Red Hat Bugzilla 2024-01-06 04:27:35 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.