Bug 1646707 - Errata needed for OVS bonds, updelay/downdelay settings ignored
Summary: Errata needed for OVS bonds, updelay/downdelay settings ignored
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 14.0 (Rocky)
Assignee: Timothy Redaelli
QA Contact: Roee Agiman
URL:
Whiteboard:
Depends On: 1646923
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 21:17 UTC by Dan Sneddon
Modified: 2019-01-11 11:54 UTC (History)
5 users (show)

Fixed In Version: openvswitch2.10-2.10.0-27.el7fdn
Doc Type: Known Issue
Doc Text:
In some OVS versions, `updelay` and `downdelay` bond settings are ignored, and the default settings are always used.
Clone Of:
: 1646923 (view as bug list)
Environment:
Last Closed: 2019-01-11 11:54:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:38 UTC

Description Dan Sneddon 2018-11-05 21:17:23 UTC
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/

Comment 7 errata-xmlrpc 2019-01-11 11:54:32 UTC
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/RHEA-2019:0045


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