Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1413516 - Wrong message when memory resource converted from MB to KB in Resource Limits
Wrong message when memory resource converted from MB to KB in Resource Limits
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.4.1
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Samuel Padgett
Yadan Pei
:
: 1457383 1506827 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-16 04:29 EST by yufchang
Modified: 2017-10-30 14:41 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When editing existing memory limits for deployments and replication controllers specified in kB, the web console could incorrectly fail validation saying that the entered value is too small for the limit range. This only happened for kB, and not other memory units. The web console has been updated to correctly handle kB units when validating values against limit ranges.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-12 15:09:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 18:50:07 EDT

  None (edit)
Description yufchang 2017-01-16 04:29:37 EST
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.
Comment 2 Abhishek Gupta 2017-02-10 12:43:32 EST
Assigning to Jessica to start with the frontend.
Comment 4 Troy Dawson 2017-02-13 17:33:10 EST
This has been merged into ocp and is in OCP v3.5.0.20 or newer.
Comment 9 errata-xmlrpc 2017-04-12 15:09:20 EDT
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
Comment 10 Samuel Padgett 2017-06-21 14:55:15 EDT
*** Bug 1457383 has been marked as a duplicate of this bug. ***
Comment 11 Jessica Forrester 2017-10-30 14:41:48 EDT
*** Bug 1506827 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.