Bug 1752412 - cannot delete the '0' number for resource limit setting
Summary: cannot delete the '0' number for resource limit setting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: cvogt
QA Contact: Ruchir Garg
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-16 10:12 UTC by shahan
Modified: 2019-10-16 06:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2753 0 None None None 2019-09-18 10:43:47 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:23 UTC

Description shahan 2019-09-16 10:12:17 UTC 
Description of problem:
 cannot delete the '0' number for resource limit setting

Version-Release number of selected component (if applicable):
 4.2.0-0.nightly-2019-09-15-052022

How reproducible:
Always

Steps to Reproduce:
1. Goto dev console-> Deploy Image page-> click 'Resource Limit' button
2. input 0 for request/limit of CPU & memory
3. try to delete
4. Set numeric value greater than zero, try to clear the input

Actual results:
3. cannot delete the 0 
4. a number 0 is always there and can not be cleared

Expected results:
the 0 number should be deleted.

Additional info:
Comment 2 shahan 2019-09-19 02:35:59 UTC 
the issue was solved. 
Verified this bug.
4.2.0-0.nightly-2019-09-18-211009
Comment 3 errata-xmlrpc 2019-10-16 06:41:11 UTC 
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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.