Red Hat Bugzilla – Bug 1561939
Backport from master OVS for "LACP: check active partner sys id"
Last modified: 2018-06-27 19:35:37 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. --- Additional comment from Red Hat Bugzilla Rules Engine on 2018-03-09 09:29:44 CET --- Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
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:2102