Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
nm-bond doesn't match connection after service restart
ip l add bond123 type bond; cat /sys/class/net/bond123/bonding/tlb_dynamic_lb
7.3: 0
7.4: 1
Version-Release number of selected component (if applicable):
1.8.0-4
How reproducible:
bond_addreses_restart_persistence
Comment 2Beniamino Galvani
2017-06-01 16:01:08 UTC
(In reply to Beniamino Galvani from comment #2)
> Created attachment 1284209[details]
> [PATCH] bond: ignore tlb_dynamic_lb for non-tlb modes
- while (options && *options) {
+ for (; options && *options; options++) {
options cannot be NULL (ever). Can we change that too?
Otherwise, lgtm
Comment 4Beniamino Galvani
2017-06-05 13:36:52 UTC
(In reply to Thomas Haller from comment #3)
> (In reply to Beniamino Galvani from comment #2)
> > Created attachment 1284209[details]
> > [PATCH] bond: ignore tlb_dynamic_lb for non-tlb modes
>
> - while (options && *options) {
> + for (; options && *options; options++) {
>
> options cannot be NULL (ever). Can we change that too?
Okay.
I realized there was a missing part: if the connection has
bond.options "mode=balance-rr,tlb_dynamic_lb=2"
(which is a weird configuration, but it is accepted), it will never match on restart because the generated connection doesn't have the 'tlb_dynamic_lb' option.
Added a commit to remove unsupported options from connection upon normalization.
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, 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-2017:2299