+++ This bug was initially created as a clone of Bug #1378000 +++ can be reproduced on 3.2.0.46, so clone to 3.2.0 Description of problem: The Pod with QoS setting cannot reach outside network on RHEL7.3 Version-Release number of selected component (if applicable): oc v3.3.0.31 kubernetes v1.3.0+52492b4 ovs-vsctl (Open vSwitch) 2.4.0 Compiled Mar 22 2016 08:42:47 DB Schema 7.12.1 Red Hat Enterprise Linux Server release 7.3 Beta (Maipo) How reproducible: always Steps to Reproduce: 1. create iperf pod with QoS setting (see Additional info for iperf.yaml file) 2. oc rsh iperf 3. ifconfig eth0 and ping 10.1.0.1 Actual results: / # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 02:42:0A:01:00:05 inet addr:10.1.0.5 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::42:aff:fe01:5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1410 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:180 (180.0 B) TX bytes:1404 (1.3 KiB) / # / # ping 10.1.0.1 PING 10.1.0.1 (10.1.0.1): 56 data bytes ^C --- 10.1.0.1 ping statistics --- 7 packets transmitted, 0 packets received, 100% packet loss Expected results: The Pod with QoS setting can reach outside network Additional info: 1. no issue found if create pod without QoS setting 2. iperf.yaml apiVersion: v1 kind: Pod metadata: name: iperf annotations: kubernetes.io/ingress-bandwidth: 3M kubernetes.io/egress-bandwidth: 2M spec: containers: - name: iperf image: yadu/hello-openshift-iperf
At this time we do not plan to work around the kernel change in the 3.2.z stream. Thus I am closing this bug as WONTFIX. Please re-open with additional justification if you wish for this decision to be re-considered.