RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1959934 - NetworkManager doesn't honour tlb_dynamic_lb=0 when creating a bonding device with mode=balance-alb
Summary: NetworkManager doesn't honour tlb_dynamic_lb=0 when creating a bonding device...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 8.5
Assignee: Wen Liang
QA Contact: Vladimir Benes
Depends On:
Blocks: 1965948
TreeView+ depends on / blocked
Reported: 2021-05-12 16:43 UTC by David Critch
Modified: 2024-04-01 12:27 UTC (History)
13 users (show)

Fixed In Version: NetworkManager-1.32.0-0.5.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1965948 (view as bug list)
Last Closed: 2021-11-09 19:30:32 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
NetworkManager journal w/ 'trace' level logging (45.03 KB, application/gzip)
2021-05-12 16:45 UTC, David Critch
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1724795 1 high CLOSED [RFE] Support for a 'source-load-balancing' bonding mode 2023-11-07 10:18:36 UTC
Red Hat Issue Tracker NMT-1081 0 None None None 2024-04-01 12:27:46 UTC
Red Hat Product Errata RHSA-2021:4361 0 None None None 2021-11-09 19:31:12 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 868 0 None closed Bond: support `tlb_dynamic_lb` in `balance-alb` mode 2021-05-31 07:33:38 UTC

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.


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