Bug 1899622 - [4.6z] configure-ovs.sh doesn't configure bonding options
Summary: [4.6z] configure-ovs.sh doesn't configure bonding options
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.6.z
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 4.6.z
Assignee: Tim Rozet
QA Contact: Ross Brattain
Depends On: 1899350
TreeView+ depends on / blocked
Reported: 2020-11-19 17:12 UTC by Tim Rozet
Modified: 2021-01-20 14:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1899350
Last Closed: 2021-01-18 17:59:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2298 0 None closed [release-4.6] Bug 1899622: backport bond options fixes 2021-02-15 17:10:26 UTC
Red Hat Product Errata RHSA-2021:0037 0 None None None 2021-01-18 17:59:58 UTC

Description Tim Rozet 2020-11-19 17:12:34 UTC
+++ This bug was initially created as a clone of Bug #1899350 +++

Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Deploy cluster with bonding enabled (using MachineConfig).
2. Wait until the nodes boot from the hard drive and finish the first boot.
3. configure-ovs.sh will create a new bonding interface ovs-if-phys0, but lacking the bonding options and ipv4.client-id

Actual results:
Bonds are configured using round robin instead of the mode specified. All bond options such as lacp_rate, updelay, miimon or xmit_hash_policy are missing

Expected results:
All bond options and ipv4.client-id setting are copied over the new bond.

Additional info:

Comment 7 errata-xmlrpc 2021-01-18 17:59:29 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 (Moderate: OpenShift Container Platform 4.6.12 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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