Bug 1300582
Summary: | pod network connection is not available after restart node service. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
Component: | Networking | Assignee: | Eric Paris <eparis> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Meng Bo <bmeng> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.1.0 | CC: | aos-bugs, bleanhar, danw, jialiu, jokerman, mmccomas, pep |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-29 20:58:26 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: |
Description
Johnny Liu
2016-01-21 08:32:44 UTC
I'm guessing that after the restart, "ovs-ofctl -O OpenFlow13 show br0" no longer shows the pod's veth device being connected to OVS. Can you confirm that? believed this might be a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1275904 https://bugzilla.redhat.com/show_bug.cgi?id=1299756 (In reply to Eric Paris from comment #2) > believed this might be a dup of > https://bugzilla.redhat.com/show_bug.cgi?id=1275904 > https://bugzilla.redhat.com/show_bug.cgi?id=1299756 It's a dup of the latter, but neither bug is a dup of the former. I was confused earlier. This is fixed by https://github.com/openshift/origin/pull/6684, but that didn't manage to land before the freeze due to test flakes. Submitted a PR against OSE enterprise-3.1 with just the minimal relevant bits here: https://github.com/openshift/ose/pull/129 (In reply to Dan Winship from comment #1) > I'm guessing that after the restart, "ovs-ofctl -O OpenFlow13 show br0" no > longer shows the pod's veth device being connected to OVS. Can you confirm > that? Yeah, you are right. Before: # ovs-ofctl -O OpenFlow13 show br0 OFPT_FEATURES_REPLY (OF1.3) (xid=0x2): dpid:0000be41c082cf4e n_tables:254, n_buffers:256 capabilities: FLOW_STATS TABLE_STATS PORT_STATS GROUP_STATS QUEUE_STATS OFPST_PORT_DESC reply (OF1.3) (xid=0x3): 1(vxlan0): addr:7a:77:fb:2b:93:cb config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 2(tun0): addr:be:82:38:c8:c8:4d config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 3(vovsbr): addr:56:40:6c:10:1d:84 config: 0 state: 0 current: 10GB-FD COPPER speed: 10000 Mbps now, 0 Mbps max 9(veth6955879): addr:fe:1c:c3:de:01:12 config: 0 state: 0 current: 10GB-FD COPPER speed: 10000 Mbps now, 0 Mbps max LOCAL(br0): addr:be:41:c0:82:cf:4e config: PORT_DOWN state: LINK_DOWN speed: 0 Mbps now, 0 Mbps max OFPT_GET_CONFIG_REPLY (OF1.3) (xid=0x5): frags=normal miss_send_len=0 After: # ovs-ofctl -O OpenFlow13 show br0 OFPT_FEATURES_REPLY (OF1.3) (xid=0x2): dpid:0000be41c082cf4e n_tables:254, n_buffers:256 capabilities: FLOW_STATS TABLE_STATS PORT_STATS GROUP_STATS QUEUE_STATS OFPST_PORT_DESC reply (OF1.3) (xid=0x3): 1(vxlan0): addr:56:bc:d9:9e:3e:17 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 2(tun0): addr:ce:8c:ad:3f:bf:19 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 3(vovsbr): addr:86:d5:1c:62:d2:02 config: 0 state: 0 current: 10GB-FD COPPER speed: 10000 Mbps now, 0 Mbps max LOCAL(br0): addr:be:41:c0:82:cf:4e config: PORT_DOWN state: LINK_DOWN speed: 0 Mbps now, 0 Mbps max OFPT_GET_CONFIG_REPLY (OF1.3) (xid=0x5): frags=normal miss_send_len=0 The issue has been fixed with the latest OSE puddle 2016-01-25.1. Versions: # openshift version openshift v3.1.1.6 kubernetes v1.1.0-origin-1107-g4c8e6f4 The pods still have network connection after node service restarted. And the pods' openflow info still exist. Bug fixed. |