Bug 1553627

Summary:	Backport from master OVS for "LACP: check active partner sys id"
Product:	Red Hat Enterprise Linux 7	Reporter:	Federico Iezzi <fiezzi>
Component:	openvswitch	Assignee:	Matteo Croce <mcroce>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ovs-qe
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	aloughla, atragler, fiezzi, mcroce
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1561939 1561969 (view as bug list)		Environment:
Last Closed:	2018-04-19 15:26:31 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:
Bug Blocks:	1561939, 1561969

Description Federico Iezzi 2018-03-09 08:29:40 UTC

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 2 Matteo Croce 2018-04-12 11:22:44 UTC

Hi,

this patch already is in the branch fast-datapath-next-rhel-7.
can we close the bug as CURRENTRELEASE?