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.

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

Description of problem:
Open vSwitch has a bug in the LACP bond implementation, such that the updelay and downdelay parameters are ignored. This bug was recently fixed, but is not yet available in any version of OVS in OSP.

Version-Release number of selected component (if applicable):
OVS 2.10

How reproducible:
100%

Steps to Reproduce:
1. Configure an OVS bond with balance-tcp mode (LACP) and updelay or downdelay configured in the options
2.
3.

Actual results:
The updelay and downdelay settings are ignored.

Expected results:
The updelay and downdelay settings should be respected.

Additional info:
The default settings seem to be working, since we haven't received any customer reports of any issues. However, this bug may come up, so we should have an errata for this issue. We are unlikely to backport these changes in OVS to previous versions of OSP, so this issue will remain until we use a newer version of OVS that includes this patch:

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

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-2019:0029