Bug 1656672 - Unexpected overriding of the resource limits
Summary: Unexpected overriding of the resource limits
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Seth Jennings
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-06 03:10 UTC by Rutvik
Modified: 2019-02-05 14:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-05 14:23:15 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rutvik 2018-12-06 03:10:53 UTC
Description of problem:

In a template called datagrid-app containing the source image: "registry.access.redhat.com/jboss-datagrid-7/datagrid72-openshift" resource limits are defined by default as:

~~~
resources:
  limits:
    memory: 1Gi
~~~

Whenever the application pod gets deployed, it is running with some unexpected resource values such as:

~~~
resources:
  limits:
    cpu: "2"
    memory: 1Gi
  requests:
    cpu: 500m
    memory: 256Mi
~~~

However, after deployment, DC and RC still shows the initial values i.e. limits.memory: 1Gi.

What made this pod to pick up the extra values? 

We have also observed that, some times the values are growing double as the original values in the template.

Note that, DC RC always stays with initial value, only pod shows inconsistent figures.

We have tried this in different namespace just for isolating the issue, we got same results as in difference in original values.

No "resource limits" are defined at the project level.

What needs to be troubleshoot here? Could this be a template bug or something else?


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