Bug 1479426 - ClusterResourceOverride doesn't seem to be working on edit resource limits
Summary: ClusterResourceOverride doesn't seem to be working on edit resource limits
Keywords:
Status: NEW
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: RFE
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-08 14:30 UTC by Dan McPherson
Modified: 2024-06-01 22:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan McPherson 2017-08-08 14:30:51 UTC
Description of problem:

When I edit resource limits.  Any values within the limit ranges seem to be accepted for cpu/memory request and limit.

Ideally I would only be able to see and set the memory limit.  But the current behavior creates a couple of problems:

1) As a user, I can easily change values that make it difficult to understand where I am going over quota by changing only CPU or memory
2) The cluster won't be fully scheduled because memory and cpu aren't guaranteed to be proportional


Version-Release number of selected component (if applicable):

Starter tier



How reproducible:


Steps to Reproduce:
1. Deploy something (Ex: ruby)
2. Edit the resource limits and only change the memory or CPU
3.

Actual results:

The change is accepted


Expected results:

ClusterResourceOverride should adjust all the values based on memory limit

Ideally only memory limit would be settable.



Additional info:

https://docs.openshift.org/latest/admin_guide/overcommit.html#configuring-masters-for-overcommitment

Comment 4 Michal Fojtik 2017-11-07 14:52:06 UTC
Dan, can you explain more detailed what you expect from this feature?


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