Bug 1807941

Summary: creating pv backing store with wrong parameters creates an unusable object in noobaa
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: aberner
Component: Multi-Cloud Object GatewayAssignee: Evgeniy Belyi <ebelyi>
Status: CLOSED ERRATA QA Contact: aberner
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3CC: ebenahar, etamir, madam, nbecker, ocs-bugs
Target Milestone: ---   
Target Release: OCS 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 09:45:56 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 aberner 2020-02-27 14:21:15 UTC
Description of problem (please be detailed as possible and provide log
snippests):
when using "oc create" to create pv-pool based backing store (with a yaml file)
the system doesnt validate the correctness of the yaml in field storage
(spec:pvPool:resources:requests:storage) and creates an unusable object.
object state in ocs dashboard is "Ready" and in Noobaa UI is initializing

Version of all relevant components (if applicable):
ocp: 4.3 ocs: 4.3 noobaa: 5.3

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?
no


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

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:
no

Steps to Reproduce:
1. create yaml with field "storage" set to a number without "Gi"
2. enter yaml to ocs through cli or ui


Actual results:
ocs object "Ready" noobaa resource "Initializing"

Expected results:
do not allow creation.

Additional info:

Comment 7 aberner 2020-03-11 09:22:55 UTC
Verified

Comment 10 errata-xmlrpc 2020-04-14 09:45:56 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:1437