Hide Forgot
Description of problem: Create a pod with QoS enabled, got below warning for pod Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 1m 1m 1 {default-scheduler } Normal Scheduled Successfully assigned iperf to openshift-127.lab.sjc.redhat.com 1m 1m 1 {kubelet openshift-127.lab.sjc.redhat.com} spec.containers{iperf} Normal Pulling pulling image "yadu/hello-openshift-iperf" 1m 1m 1 {kubelet openshift-127.lab.sjc.redhat.com} spec.containers{iperf} Normal Pulled Successfully pulled image "yadu/hello-openshift-iperf" 1m 1m 1 {kubelet openshift-127.lab.sjc.redhat.com} spec.containers{iperf} Normal Created Created container with docker id 4e337a82ab5b 1m 1m 1 {kubelet openshift-127.lab.sjc.redhat.com} spec.containers{iperf} Normal Started Started container with docker id 4e337a82ab5b 1m 1m 3 {kubelet openshift-127.lab.sjc.redhat.com} Warning NilShaper Pod requests bandwidth shaping, but the shaper is undefined Version-Release number of selected component (if applicable): openshift v3.2.0.15 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 How reproducible: Always Steps to Reproduce: 1. Create the pod with QoS enabled apiVersion: v1 kind: Pod metadata: name: iperf annotations: kubernetes.io/ingress-bandwidth: 3M kubernetes.io/egress-bandwidth: 3M spec: containers: - name: iperf image: yadu/hello-openshift-iperf 2. Describe the pod Actual results: Same as Description Expected results: Should not show such warning
This is a bug in upstream kube that was fixed with https://github.com/kubernetes/kubernetes/pull/22827 and won't be present in origin until the next rebase on kubernetes.
I assume this is in now?
(In reply to Ben Bennett from comment #2) > I assume this is in now? Yeah, it should be in kube 1.3 and later, I believe.
(and thus also in OpenShift 3.3 and later)