Bug 1891189

Summary:	[LSO] max device limit is accepting negative values. PVC is not getting created and no error is shown
Product:	OpenShift Container Platform	Reporter:	Pratik Surve <prsurve>
Component:	Console Storage Plugin	Assignee:	Bipul Adhikari <badhikar>
Status:	CLOSED ERRATA	QA Contact:	Pratik Surve <prsurve>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.6	CC:	aos-bugs, ebenahar, nberry, nthomas, ocs-bugs
Target Milestone:	---
Target Release:	4.7.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:	2021-02-24 15:28:00 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 Pratik Surve 2020-10-24 06:33:27 UTC

Description of problem:
[LSO] max device limit is accepting negative values 

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-10-17-040148

How reproducible:
always

Steps to Reproduce:
1. Deploy OCP 4.6
2. Deploy ocs 4.6
3. Create storagecluster from UI
4. use a negative value for max device limit  

Actual results:
Max device limit accept's negative values and no error is shown, that cause PV not getting created

Expected results:
UI should not accept the negative value and a proper error msg should be shown

Additional info:

Comment 1 Bipul Adhikari 2020-12-10 11:39:08 UTC

Priority Low => Does not hamper user interaction.
Targetted to be fixed this sprint.

Comment 7 errata-xmlrpc 2021-02-24 15:28:00 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633