Bug 1479426 - ClusterResourceOverride doesn't see to be working on edit resource limits
ClusterResourceOverride doesn't see to be working on edit resource limits
Status: NEW
Product: OpenShift Online
Classification: Red Hat
Component: RFE (Show other bugs)
3.x
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Abhishek Gupta
: OnlineStarter
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-08 10:30 EDT by Dan McPherson
Modified: 2017-11-07 09:52 EST (History)
4 users (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Dan McPherson 2017-08-08 10:30:51 EDT
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 09:52:06 EST
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.