Bug 1479426

Summary: ClusterResourceOverride doesn't seem to be working on edit resource limits
Product: OpenShift Online Reporter: Dan McPherson <dmcphers>
Component: RFEAssignee: Abhishek Gupta <abhgupta>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.xCC: aos-bugs, decarr, mfojtik, xtian
Target Milestone: ---Keywords: OnlineStarter
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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?