RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

Hi,

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