Bug 1855118 - Killing ovs-vswitchd cause some ovs openflows lost [NEEDINFO]
Summary: Killing ovs-vswitchd cause some ovs openflows lost
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.z
Assignee: Aniket Bhat
QA Contact: huirwang
URL:
Whiteboard:
Depends On: 1852618
Blocks: 1855119
TreeView+ depends on / blocked
 
Reported: 2020-07-09 02:16 UTC by huirwang
Modified: 2020-07-30 18:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1848374
: 1855119 (view as bug list)
Environment:
Last Closed: 2020-07-30 18:56:59 UTC
Target Upstream Version:
lmohanty: needinfo? (bbennett)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sdn pull 160 0 None closed Bug 1855118: [release-4.5] Add support for --may-exist when adding the bridge in sdn 2020-12-18 07:56:09 UTC
Red Hat Product Errata RHBA-2020:3028 0 None None None 2020-07-30 18:57:33 UTC

Comment 2 Lalatendu Mohanty 2020-07-09 13:17:58 UTC 
As per https://github.com/openshift/openshift-docs/issues/19847#issuecomment-656030450 this issue maybe happen when upgrading the cluster. But from teh description of the bug does not have any information about upgrades. Can you please confirm?
Comment 3 Anurag saxena 2020-07-09 17:41:43 UTC 
There is an upgrade bug depicting similar behavior https://bugzilla.redhat.com/show_bug.cgi?id=1852618. I was not able to repro this ovs lost flows issue on OPEN PR https://github.com/openshift/sdn/pull/158. While its still not sure (from dev) whether this change could solve upgrade issue or not but it looks promising and can be verified for upgrade as well once merged.
Comment 9 errata-xmlrpc 2020-07-30 18:56:59 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:3028
Note You need to log in before you can comment on or make changes to this bug.