Bug 1833603

Summary:	[sriov]Should block user set logLevel to value out range
Product:	OpenShift Container Platform	Reporter:	zhaozhanqi <zzhao>
Component:	Networking	Assignee:	Peng Liu <pliu>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	bbennett, dosmith
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:36:32 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 zhaozhanqi 2020-05-09 02:44:09 UTC

Description of problem:
Now, set the logLevel can be set to -1, 
I0508 13:19:09.972730   39921 daemon.go:167] Set log verbose level to: -1


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

How reproducible:
always

Steps to Reproduce:
1. edit sriovoperatorconfigs to set the logLevel: -1
2.
3.

Actual results:


Expected results:

should block user set no meaningful value for logLevel

Additional info:

Comment 4 zhaozhanqi 2020-05-18 03:49:08 UTC

seems the error message is not correct.  
when 'set the logLevel: 3' and error message is `* spec.logLevel: Invalid value: 2`, 
when set to 'logLevel -3', the error message is '* spec.logLevel: Invalid value: 0'

Comment 5 zhaozhanqi 2020-05-28 09:48:36 UTC

Verified this issue on 4.5.0-202005271737
when set incorrect value. eg 3.  the error message show: pec.logLevel in body should be less than or equal to 2

Comment 6 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