Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1501960 - Remove the use of CPU limits by default
Remove the use of CPU limits by default
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.6.0
All All
high Severity high
: ---
: 3.6.z
Assigned To: Jeff Cantrill
Junqi Zhao
: OpsBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-13 11:13 EDT by Peter Portante
Modified: 2017-12-07 02:13 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-07 02:13:19 EST
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/openshift-ansible/pull/5748 None None None 2017-10-16 09:31 EDT
Github openshift/openshift-ansible/pull/5815 None None None 2017-10-23 10:33 EDT
Github openshift/origin-aggregated-logging/pull/726 None None None 2017-10-16 14:36 EDT
Red Hat Product Errata RHSA-2017:3389 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise security, bug fix, and enhancement update 2017-12-07 07:09:10 EST

  None (edit)
Description Peter Portante 2017-10-13 11:13:03 EDT
We should not be specifying a CPU limit for infrastructure pods by default.  Instead, we should be specifying a proper CPU request to ensure a pod is scheduled on a node where a minimum CPU resources are available.
Comment 1 Jeff Cantrill 2017-10-16 14:36:02 EDT
Adding ref to 3.6 origin logging PR. Needed before ansible change. openshift/origin-aggregated-logging/pull/726
Comment 2 openshift-github-bot 2017-10-20 16:58:01 EDT
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/578ac5b348fa3e9c7d0d05e3a0f579839ecd79dd
Use "requests" for CPU resources instead of limits

We now use a CPU request to ensure logging infrastructure pods are
not capped by default for CPU usage. It is still important to ensure
we have a minimum amount of CPU.

We keep the use of the variables *_cpu_limit so that the existing
behavior is maintained.

Note that we don't want to cap an infra pod's CPU usage by default,
since we want to be able to use the necessary resources to complete
it's tasks.

Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
Comment 4 Junqi Zhao 2017-10-24 02:52:06 EDT
Please change to ON_QA, issue is fixed
Tested scenarios:
1. ops enabled cluster
2. mux client

It uses "resources.requests.cpu" for CPU resources instead of "resources.limits.cpu" now

But there is one defect: https://bugzilla.redhat.com/show_bug.cgi?id=1505683, 
this defect is not related to BZ 1501960, so close BZ 1501960.


images:
logging-kibana:v3.6.173.0.59-1
logging-elasticsearch:v3.6.173.0.59-1
logging-fluentd:v3.6.173.0.59-1
logging-auth-proxy:v3.6.173.0.59-1
logging-curator:v3.6.173.0.59-1


# rpm -qa | grep openshift-ansible
openshift-ansible-filter-plugins-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-docs-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-lookup-plugins-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-callback-plugins-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-playbooks-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-3.6.173.0.59-1.git.0.0e31372.el7.noarch
openshift-ansible-roles-3.6.173.0.59-1.git.0.0e31372.el7.noarch
Comment 5 Junqi Zhao 2017-10-24 20:22:03 EDT
set it to VERIFIED as per Comment 4
Comment 8 errata-xmlrpc 2017-12-07 02:13:19 EST
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.

https://access.redhat.com/errata/RHSA-2017:3389

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