Bug 1656672

Summary: Unexpected overriding of the resource limits
Product: OpenShift Container Platform Reporter: Rutvik <rkshirsa>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED NOTABUG QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, rkshirsa, zhuchkov.alex
Target Milestone: ---   
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: 2019-02-05 14:23:15 UTC 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 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?