Bug 1558155
| Summary: | Limit ranges are being applied with cpu-cfs-quota set to false | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Derek Carr <decarr> |
| Component: | Node | Assignee: | Seth Jennings <sjenning> |
| Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.9.0 | CC: | aos-bugs, avagarwa, decarr, dma, jokerman, mmccomas, tibrahim |
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Fixes an issue on the node where setting disabling cpu-cfs-quota did not prevent cpu cfs limits from being set on pods when cgroups-per-qos was enabled.
|
Story Points: | --- |
| Clone Of: | 1554471 | Environment: | |
| Last Closed: | 2018-05-17 06:42:42 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: | |||
| Bug Depends On: | 1554471, 1558157 | ||
| Bug Blocks: | |||
|
Comment 1
Seth Jennings
2018-04-10 03:37:18 UTC
Verify on ocp v3.9.20 Steps to verify: Set cpu-cfs-quota=true in /etc/origin/node/node-config.yaml kubeletArguments: cpu-cfs-quota: - 'true' //Case 1 (cpu-cfs-quota=true + without limits) 1. Create a pod without limits 2. rsh into pod run 'dd if=/dev/zero of=/dev/null' 3. In another terminal rsh into pod and run 'while true; do sleep 4; ps aux|grep dd ; done' The cpu usage is about 99% for one core sh-4.2# while true; do sleep 4; ps aux|grep dd ; done root 19 98.0 0.0 4348 344 ? R+ 08:59 0:24 dd if=/dev/zero of=/dev/null 4. The the host which the pod running, using `htop` to watch the cpu usage. one of the four cpu core usage is about 99% //Case 2 (cpu-cfs-quota=true + with limits) 1. Create a pod with limits.cpu=500m 2. rsh into pod run 'dd if=/dev/zero of=/dev/null' 3. In another terminal rsh into pod and run 'while true; do sleep 4; ps aux|grep dd ; done' The cpu usage is about 50% for one core 4. The the host which the pod running, using `htop` to watch the cpu usage. one of the four cpu core usage is about 50% //Case 3 (cpu-cfs-quota=false + without limits) 1. Create a pod without limits.cpu=500m 2. rsh into pod run 'dd if=/dev/zero of=/dev/null' 3. In another terminal rsh into pod and run 'while true; do sleep 4; ps aux|grep dd ; done' The cpu usage is about 99% for one core 4. The the host which the pod running, using `htop` to watch the cpu usage. one of the four cpu core usage is about 99% //Case 4 (cpu-cfs-quota=false + with limits) 1. Create a pod without limits 2. rsh into pod run 'dd if=/dev/zero of=/dev/null' 3. In another terminal rsh into pod and run 'while true; do sleep 4; ps aux|grep dd ; done' The cpu usage is about 99% for one core. 4. The the host which the pod running, using `htop` to watch the cpu usage. one of the four cpu core usage is about 99%. 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/RHBA-2018:1566 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |