Bug 1813654

Summary:	[NooBaa UI] No minimum size restriction in the Kubernetes Pool creation dialog
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Ben Eli <belimele>
Component:	Multi-Cloud Object Gateway	Assignee:	Ohad <omitrani>
Status:	CLOSED ERRATA	QA Contact:	Ben Eli <belimele>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3	CC:	etamir, nbecker, ocs-bugs, ratamir
Target Milestone:	---
Target Release:	OCS 4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.4.0-410	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-04 12:54:37 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 Ben Eli 2020-03-15 09:17:34 UTC

Description of problem (please be detailed as possible and provide log
snippests):
When creating a new Kubernetes pool using the "Deploy Kubernetes Pool" button under the "Resources" UI tab, the user is prompted to enter a name, and then a Node PV Size. The bare minimum needed in order for the system to work is 16GB per pod, but the user can insert whatever number they wish. 

Version of all relevant components (if applicable):
NB 
5.3.0-df3abc2
OCS
4.3.0-376.ci

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No

Is there any workaround available to the best of your knowledge?
Insert a size larger than 16GB

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Actual results:
Backingstore creation is possible

Expected results:
Backingstore creation should be blocked

Additional info:

Comment 2 Ohad 2020-03-24 19:37:41 UTC

Fixed in upstream PR (see links)

Comment 8 errata-xmlrpc 2020-06-04 12:54:37 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:2393