Red Hat Bugzilla – Bug 1558155
Limit ranges are being applied with cpu-cfs-quota set to false
Last modified: 2018-05-17 10:50:12 EDT
This was picked by the bot: https://github.com/openshift/ose/commit/59f6168a8805c72804ec697739529d76aa81009b
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%.
In comment 3, we have verified the bug.
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