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:
Fixed in upstream PR (see links)
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