Hide Forgot
+++ This bug was initially created as a clone of Bug #1899350 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Always 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:
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. https://access.redhat.com/errata/RHSA-2021:0037