Bug 1959934

Summary: NetworkManager doesn't honour tlb_dynamic_lb=0 when creating a bonding device with mode=balance-alb
Product: Red Hat Enterprise Linux 8 Reporter: David Critch <dcritch>
Component: NetworkManagerAssignee: Wen Liang <wenliang>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: high Docs Contact:
Priority: high    
Version: 8.4CC: acardace, atragler, bgalvani, bperkins, danken, fge, lrintel, phoracek, rkhan, sukulkar, thaller, till, vbenes
Target Milestone: betaKeywords: Triaged, ZStream
Target Release: 8.5   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: NetworkManager-1.32.0-0.5.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1965948 (view as bug list) Environment:
Last Closed: 2021-11-09 19:30:32 UTC Type: Bug
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:    
Bug Blocks: 1965948    
Description Flags
NetworkManager journal w/ 'trace' level logging none

Description David Critch 2021-05-12 16:43:35 UTC
Description of problem:
We have a customer that needs to use bonding mode balance-alb, with the tlb_dynamic_lb setting set to 0. This device is configured via NetworkManager. After creating the bond, tlb_dynamic_lb is still set to 1.

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

How reproducible:

Steps to Reproduce:
1. Create a bond, e.g.:
nmcli conn add type bond ifname bond0 con-name bond0 bond.options "mode=balance-alb,miimon=100,xmit_hash_policy=5,tlb_dynamic_lb=0" master brcnv connection.autoconnect no
2. cat /sys/class/net/bond0/bonding/tlb_dynamic_lb

Actual results:
$ cat /sys/class/net/bond0/bonding/tlb_dynamic_lb 

Expected results:
$ cat /sys/class/net/bond0/bonding/tlb_dynamic_lb 

Additional info:
Attaching NM debug logs

Comment 1 David Critch 2021-05-12 16:45:13 UTC
Created attachment 1782469 [details]
NetworkManager journal w/ 'trace' level logging

Comment 13 errata-xmlrpc 2021-11-09 19:30: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 (Moderate: NetworkManager security, bug fix, and enhancement 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.