Bug 1561969 – Backport from master OVS for "LACP: check active partner sys id"

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1561969 - Backport from master OVS for "LACP: check active partner sys id"

Summary:	Backport from master OVS for "LACP: check active partner sys id"

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openvswitch (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	z3
Target Release:	12.0 (Pike)
Assigned To:	Timothy Redaelli
QA Contact:	Ofer Blaut
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:	1553627
Blocks:
	Show dependency tree / graph

Reported:	2018-03-29 05:28 EDT by Timothy Redaelli
Modified:	2018-10-17 04:58 EDT (History)
CC List:	13 users (show)

See Also:
Fixed In Version:	openvswitch-2.7.4-6.git20180112.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1553627
Environment:
Last Closed:	2018-08-20 08:57:43 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2524	None	None	None	2018-08-20 08:58 EDT

Groups: None (edit)

Description Timothy Redaelli 2018-03-29 05:28:14 EDT

+++ This bug was initially created as a clone of Bug #1553627 +++

Description of problem:

Hi there,
I would like to ask to backport to all our supported OVS versions the following upstream commit.
https://github.com/openvswitch/ovs/commit/6f50056c4fe7e1ae2eb3baa9086796686dc6e0e7

https://patchwork.ozlabs.org/patch/845107/

As described in the commit comment, if a switch member of the lag goes down (for a reboot, maintenance etc) LACP goes down as well.

Version-Release number of selected component (if applicable):
This issue applies to any OVS with the exception of 2.9 and master.
This issue definitely impacts kernel datapath. I'm not sure about netdev.

How reproducible:
Setup a plain OVS, create an LACP bond, shutdown/reboot a physical switch.

Actual results:
OVS LACP goes down and it stops forwarding any data until the original member is back to normal.

Expected results:
LACP is designed for not going down.

Comment 11 errata-xmlrpc 2018-08-20 08:57:43 EDT

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/RHSA-2018:2524

Note You need to log in before you can comment on or make changes to this bug.