Bug 1462338
Summary: | [3.5] pod-to-pod connectivity lost after rescaling with ovs-multitenant | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ben Bennett <bbennett> |
Component: | Networking | Assignee: | Ben Bennett <bbennett> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.5.0 | CC: | akaiser, aos-bugs, bbennett, bmeng, danw, dcbw, eparis, gsapienz, javier.ramirez, mark.vinkx, nnosenzo, pdwyer, rhowe, rromerom, sjr, tibrahim, tmanor, vcorrea, weliang |
Target Milestone: | --- | ||
Target Release: | 3.5.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: We were incorrectly removing VNID allow rules before they were really unused. It appears that when containers had startup errors it can cause the tracking to get out of sync.
Consequence: The rules that allowed communication for a namespace were removed early, so that if there were still pod in that namespace on the node, they could not communicate with one another.
Fix: Change the way that the tracking is done so that we avoid the nasty edge cases around pod creation / deletion failures.
Result: The VNID tracking does not fail so traffic flows.
|
Story Points: | --- |
Clone Of: | 1454948 | Environment: | |
Last Closed: | 2017-07-11 10:47:38 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: | 1454948 | ||
Bug Blocks: | 1267746 |
Comment 1
markv
2017-06-19 08:59:38 UTC
@markv this is a private repository, that's why you can't access to it. Regards Ruben It's a backport of https://github.com/openshift/origin/pull/14560 Do not see network connectivity issue when tested in: oc v3.5.5.28 kubernetes v1.5.2+43a9be4 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-2017:1640 *** Bug 1464657 has been marked as a duplicate of this bug. *** |