Description of problem: Wrong message when memory resource converted from MB to kB in Resource Limits Version-Release number of selected component (if applicable): OpenShift Master:v3.4.0.39 (online version 3.4.0.12) Kubernetes Master:v1.4.0+776c994 How reproducible: Always Steps to Reproduce: cat >> hello-deployment-1.yaml << EOF apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-openshift spec: replicas: 4 template: metadata: labels: app: hello-openshift spec: containers: - name: hello-openshift image: openshift/hello-openshift ports: - containerPort: 80 strategy: rollingUpdate: maxSurge: 3 maxUnavailable: 2 type: RollingUpdate EOF 1.Create a project; 2.oc create -f hello-deployment-1.yaml; 3.Go to Applications -> Deployments -> <Deployment name> page -> Actions -> Set Resource Limits; 4. Set Memory to 900.9 MB; 5. Save; 6. Open Set Resource Limits again to check, and try to modify again. Actual results: 5. Save successfully; 6. Display “900900kB”, but memory frame turn red and prompt error memory "can not be less than 250 MiB. Memory limit total for all containers is less than pod minimum (250 MiB)." Button "save" is not available. Expected results: 900900kB is a valid value. No error message is displayed, button ‘save’ is available. Additional info: 1. When you input 900900000 kB, button ‘save’ become available,Maybe the unit shoud be B, not KB. 2. The convert between MiB to mB is correct.
Assigning to Jessica to start with the frontend.
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/8427b2e10f490a5ea5c0232dd4949bff70e204c7 Bug 1413516: Correctly handle suffix `k` in `usageValue` filter Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1413516
This has been merged into ocp and is in OCP v3.5.0.20 or newer.
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-2017:0884
*** Bug 1457383 has been marked as a duplicate of this bug. ***
*** Bug 1506827 has been marked as a duplicate of this bug. ***