Issue 1 is something we will look into fixing in the UI by only showing the units that fit within the limit range that exists, we will probably do client side validation of this based on the limit range as well.
Issues 2 and 3 are problems with the kube API server, I've opened
I will clone a separate bug to the kubernetes component to track those.
https://bugzilla.redhat.com/show_bug.cgi?id=1414465 will track issues 2 and 3
Moving this to OCP since it is not an issue specific to Online, it just surfaced in online because there are default limit ranges in place.
Fix to issue 1 went in with https://github.com/openshift/origin-web-console/pull/1134
This has been merged into ocp and is in OCP v22.214.171.124 or newer.
Will check this when dev-preview-stg environment is upgraded to 3.5
@zhezli can you also verify it against OCP, the bug was in OCP and was not specific to Online, I'd rather not wait till stg env is updated to verify that this is fixed.
You can recreate the issue by using the same limit range in your project that is used for dev-preview-stg. The main part is that the storage request min and max were equal and set to 1Gi
(In reply to Jessica Forrester from comment #8)
> You can recreate the issue by using the same limit range in your project
> that is used for dev-preview-stg. The main part is that the storage request
> min and max were equal and set to 1Gi
Checked with OCP 126.96.36.199 , When storage request min and max are both set to 1G, on create pvc page, the size is set to 1G automatically and can not be changed.
This has been merged into ocp and is in OCP v188.8.131.52 or newer.
Please re-test this on v184.108.40.206 or newer. There was a problem with the merge in 220.127.116.11.
(In reply to Troy Dawson from comment #12)
> This has been merged into ocp and is in OCP v18.104.22.168 or newer.
> Please re-test this on v22.214.171.124 or newer. There was a problem with the
> merge in 126.96.36.199.
See attachment please
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.