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.

the sysctl values "activate_slave" for bond can only be set if the slave interface is actually enslaved. Otherwise, kernel logs a warning. Also, writing the sysctl will fail, and NetworkManager also logs a warning.

Avoid that.


Backport https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e48c908e8cb5e0b426a4bf8d99608f73cd7890e4 to rhel-8.3

reproduce: on "1.26.0-1", activate a bond master that has "active_slave" option set.

- Note the warning in the logs. The only problem is that NM tries to do something that it shouldn't and that doesn't work. That causes error messages in log.

- also note, that if you later activate the slave, the "active_slave" option gets set. But that is unrelated to this issue, and we should have CI for that already.

I don't think this requires a dedicated CI test. We already have CI tests for various bond-cases, including "active_slave" (don't we?).

(In reply to Thomas Haller from comment #2)
> I don't think this requires a dedicated CI test. We already have CI tests
> for various bond-cases, including "active_slave" (don't we?).

yeah we have one 
bond_set_active_backup_options

https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/blob/master/nmcli/features/bond.feature#L1184

CI test modified to catch the error now
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/611

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 (NetworkManager 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.

https://access.redhat.com/errata/RHBA-2020:4499