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:
https://ceph-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OCS%20Build%20Pipeline%204.3/93/ contains the fix
Verified
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