*** Bug 1582486 has been marked as a duplicate of this bug. ***

Verify on v3.7.51


1. Set cpu-cfs-quota=false in /etc/origin/node/node-config.yaml then create a pod check the value of cpu.cfs_quota_us
[root@ip-172-18-15-169 ~]# oc get po -n dma1
NAME              READY     STATUS    RESTARTS   AGE
burstable-p95td   1/1       Running   0          3m
[root@ip-172-18-15-169 ~]# oc get po -n dma1 -o yaml|grep uid
      openshift.io/scc: anyuid
    uid: 20e73511-623f-11e8-96f1-0ee986d138ca
[root@ip-172-18-15-169 ~]# cat /sys/fs/cgroup/cpu/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod20e73511_623f_11e8_96f1_0ee986d138ca.slice/cpu.cfs_quota_us 
-1

2. Set cpu-cfs-quota=true in /etc/origin/node/node-config.yaml then create a pod check the value of cpu.cfs_quota_us
[root@ip-172-18-15-169 ~]# oc get po -n dma -w
NAME              READY     STATUS              RESTARTS   AGE
burstable-t9f62   0/1       ContainerCreating   0          6s
burstable-t9f62   1/1       Running   0         9s
[root@ip-172-18-15-169 ~]# oc get po -n dma -o yaml|grep uid
      openshift.io/scc: anyuid
    uid: e5e3caa1-623c-11e8-96f1-0ee986d138ca
[root@ip-172-18-11-1 ~]# cat /sys/fs/cgroup/cpu/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode5e3caa1_623c_11e8_96f1_0ee986d138ca.slice/cpu.cfs_quota_us 
100000

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:1798