Bug 1765220 - [3.11] After OCP upgrade, a pod vethXXX interface was not re-added to the bridge br0
Summary: [3.11] After OCP upgrade, a pod vethXXX interface was not re-added to the bri...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Aniket Bhat
QA Contact: huirwang
URL:
Whiteboard:
Depends On: 1792164 1806648
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-24 14:40 UTC by Jonas Nordell
Modified: 2024-03-25 15:28 UTC (History)
28 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1792164 (view as bug list)
Environment:
Last Closed: 2020-03-20 00:12:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24318 0 None closed [release-3.11] pkg/network: Fix pod startup reattach/kill loop 2021-02-04 11:42:11 UTC
Github openshift origin pull 24585 0 None closed Bug 1765220: Fix pod startup reattach/kill loop 2021-02-04 11:42:11 UTC
Github openshift origin pull 24673 0 None closed Bug 1765220: Use sandbox id instead of getting it using pod key 2021-02-04 11:42:11 UTC
Github openshift sdn pull 58 0 'None' closed Fix pod startup reattach/kill loop 2021-02-04 11:42:12 UTC
Red Hat Knowledge Base (Solution) 4626241 0 None None None 2020-03-09 11:57:46 UTC
Red Hat Product Errata RHBA-2020:0793 0 None None None 2020-03-20 00:12:54 UTC

Comment 7 Dan Winship 2019-11-08 11:22:13 UTC 
probably fixed by sdn #58
Comment 16 Dan Winship 2019-12-03 13:55:24 UTC 
What is the name of the pod that's not being reattached?

sdn logs show:

W1202 15:49:04.840316   21968 pod.go:224] No network information for pod networkpolicy/postgresql-4-tsjgz
W1202 15:49:04.840345   21968 pod.go:224] No network information for pod openshift-logging/logging-fluentd-wbcl7
W1202 15:49:04.840353   21968 pod.go:224] No network information for pod openshift-monitoring/node-exporter-spr42
W1202 15:49:04.840362   21968 pod.go:224] No network information for pod openshift-node/sync-9vkvf
W1202 15:49:04.840371   21968 pod.go:224] No network information for pod openshift-sdn/ovs-ptf4v
W1202 15:49:04.840382   21968 pod.go:224] No network information for pod openshift-sdn/sdn-6bnp2

most of those are hostNetwork pods and the "no network information" is not actually a problem. (In 4.x we don't log anything in that case but we didn't backport that fix to 3.11.) Is "networkpolicy/postgresql-4-tsjgz" your missing pod?

There are no "Reattaching pod '%s/%s' to SDN" messages after this, implying that it didn't even try to reattach anything. (Which would make sense if there was actually no network information for any pod that it could have tried to reattach.)


This may be the thing that was fixed by https://github.com/openshift/sdn/pull/58, which has not been backported yet...
Comment 29 Venkatesh Kavtikwar 2020-01-07 12:24:39 UTC 
Adding To Ksenija ..

Customer is currently on 3.11.154. 

We mean to ask, Can you confirm if "3.11.157" contains the fix?
Comment 30 Venkatesh Kavtikwar 2020-01-07 12:25:15 UTC 
Adding To Ksenija ..

Customer is currently on 3.11.154. 

We mean to ask, Can you confirm if "3.11.157" contains the fix?
Comment 31 Dan Winship 2020-01-07 13:56:44 UTC 
3.11.147 had some fixes for similar problems. No release since then has had any further fixes.
Comment 37 zhaozhanqi 2020-01-17 09:52:03 UTC 
*** Bug 1792164 has been marked as a duplicate of this bug. ***
Comment 54 Aniket Bhat 2020-02-26 16:04:27 UTC 
This is waiting on a 4.2 backport.

4.2 PR: https://github.com/openshift/sdn/pull/110
3.11 PR: https://github.com/openshift/origin/pull/24585
Comment 70 errata-xmlrpc 2020-03-20 00:12:40 UTC 
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-2020:0793
Note You need to log in before you can comment on or make changes to this bug.