Bug 1833605 - [sriov]Add the more detail explain to CRD for logLevel
Summary: [sriov]Add the more detail explain to CRD for logLevel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: All
OS: All
medium
low
Target Milestone: ---
: 4.5.0
Assignee: Peng Liu
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-09 02:50 UTC by zhaozhanqi
Modified: 2020-07-13 17:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:36:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 210 0 None closed Bug 1833603: Limit the range of logLevel and add detailed description 2020-07-03 05:41:52 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:37:23 UTC

Description zhaozhanqi 2020-05-09 02:50:00 UTC 
Description of problem:

currently, the logLevel explain only show: 
     Flag to control the log verbose level of the operator

better add more detail like:
what's the value range. and what's the meaning for each value. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. oc explain sriovoperatorconfigs.spec.logLevel
2.
3.

Actual results:


Expected results:
better give more detail value explain.

Additional info:
Comment 1 zhaozhanqi 2020-05-29 08:22:04 UTC 
Verified this bug 4.5.0-202005271737

oc explain SriovOperatorConfig.spec.logLevel
KIND:     SriovOperatorConfig
VERSION:  sriovnetwork.openshift.io/v1

FIELD:    logLevel <integer>

DESCRIPTION:
     Flag to control the log verbose level of the operator. Set to '0' to show
     only the basic logs. And set to '2' to show all the available logs.
Comment 3 errata-xmlrpc 2020-07-13 17:36:32 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:2409
Note You need to log in before you can comment on or make changes to this bug.