Description of problem:
Setting Build Defaults (requests/limits) has no effect on actual build pod.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up Build Defaults
oc describe build.config.openshift.io/cluster
Annotations: release.openshift.io/create-only: true
API Version: config.openshift.io/v1
Creation Timestamp: 2019-07-14T14:51:04Z
Resource Version: 570536
Self Link: /apis/config.openshift.io/v1/builds/cluster
2. Set up a LimitRange (in a Project Request Template) and create a new project
oc describe limits wk-builds-core-resource-limits
Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio
---- -------- --- --- --------------- ------------- -----------------------
Container memory 6Mi 6Gi 512Mi 1Gi -
Container cpu - - 250m 500m -
Pod memory 6Mi 12Gi - - -
2. Start a new build
oc new-app https://github.com/wkulhanek/rhte-app.git
3. Check the build pod
oc describe pod rhte-app-1-build
The pod uses the defaults from the Limit Range rather than the build defaults.
The pod uses the defaults from the build defaults therefore not needing to fall back on the defaults from the limit range
Marking this as a regression from 3.11, blocker for 4.2.0
FYI, @Wolfgang Kulhanek your Build Default config incorrect, should be
@wewang My build defaults are straight from the docs:
This is exactly what I have:
I don't see a difference to what you are writing. The only difference I see is "Resources" in your example vs "resources" in mine and the docs.
Oh I see. I submitted the "oc describe" and you gave me YAML. So the YAML should be fine.
@Ricardo: I keep getting notification that info is needed from me - but I don't see what. Do you actually need something from me?
@Ricardo Maraschini After waiting ds rollout, config applied to build pod, thanks
$oc describe pod/ruby-hello-world-1-build
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.