Description of problem (please be detailed as possible and provide log snippests): When creating a new PVC BackingStore via the management console (Operators -> Installed Operators -> OCS -> Backing Store -> Create -> Provider=PVC) The Volume Size can be set to lower than 16GB, which is the bare minimum needed for the feature to work. The creation works in the end, but uses 20~GBs (which is defined as the minimum in the CRD. Changed to 16 as part of 1813655) even if the user chose 1GB. Version of all relevant components (if applicable): OCS 4.3.0-376.ci OCP 4.3.0-0.nightly-2020-03-16-193416 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? 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 Actual results: Creation is possible with any size the user wishes Expected results: Creation should be blocked in case the size given is lower than 16GB
The frontend should not be handling the validation of the minimum size. backend should reject it if the minimum size limit is not fulfilled in the request sent by the console UI. Moving back to MCG>
Creation is allowed, backingstore enters a rejected state with the message "NooBaa BackingStore "pvcback" is in rejected phase due to insufficient size, min is 16000000000=16GB" Verified. OCS v4.5.0-493.ci OCP v4.5.0-0.nightly-2020-07-18-024505
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 (Red Hat OpenShift Container Storage 4.5.0 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/RHBA-2020:3754