Bug 1899622

Summary: [4.6z] configure-ovs.sh doesn't configure bonding options
Product: OpenShift Container Platform Reporter: Tim Rozet <trozet>
Component: Machine Config OperatorAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Ross Brattain <rbrattai>
Severity: high Docs Contact:
Priority: high    
Version: 4.6.zCC: achernet, cpaquin, jhuddles, mkrejci, mnguyen, mzamot, sreichar, wking
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1899350 Environment:
Last Closed: 2021-01-18 17:59:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1899350    
Bug Blocks:    

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.