Bug 1765220
| Summary: | [3.11] After OCP upgrade, a pod vethXXX interface was not re-added to the bridge br0 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jonas Nordell <jnordell> | |
| Component: | Networking | Assignee: | Aniket Bhat <anbhat> | |
| Networking sub component: | openshift-sdn | QA Contact: | huirwang | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | unspecified | CC: | aivaraslaimikis, akrastin, anbhat, andbartl, annelson, bbennett, ckoep, danw, dmoessne, dyocum, huirwang, igreen, jdelft, jdesousa, jkaur, joboyer, knaeem, kpelc, mrobson, openshift-bugs-escalate, palonsor, rhowe, sburke, scuppett, skrenger, vkavtikw, vlaad, zzhao | |
| Version: | 3.11.0 | |||
| Target Milestone: | --- | |||
| Target Release: | 3.11.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1792164 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-20 00:12:40 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: | ||||
| Bug Depends On: | 1792164, 1806648 | |||
| Bug Blocks: | ||||
|
Comment 7
Dan Winship
2019-11-08 11:22:13 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... Adding To Ksenija .. Customer is currently on 3.11.154. We mean to ask, Can you confirm if "3.11.157" contains the fix? Adding To Ksenija .. Customer is currently on 3.11.154. We mean to ask, Can you confirm if "3.11.157" contains the fix? 3.11.147 had some fixes for similar problems. No release since then has had any further fixes. *** Bug 1792164 has been marked as a duplicate of this bug. *** 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 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 |