Systemd LACP issue on RL 9.1

Hi to all,
I setup one bond with LACP on RL9.1 and have a lot of errors and the bond goes up and down.
After I find this issue on systemd: [systemd >=242] LACP no longer works on NetworkManager bond interfaces · Issue #15208 · systemd/systemd · GitHub
that solve my problems.
It is possible to use same pathc mentioned for RHEL?

Rocky builds from RHEL sources. The workflow is something like:

  1. Issue is reported on RHEL
  2. Red Hat writes a patch
  3. Red Hat builds and releases package (and source) for RHEL
  4. Rocky builds and releases package for Rocky Linux
  5. User installs the updated package

The rpm -q --changelog systemd on el9 shows:

* Wed Feb 23 2022 systemd maintenance team <systemd-maint@redhat.com> - 250-4
- udev/net-setup-link: change the default MACAddressPolicy to "none" (#2009237)

That is, Red Hat has written a patch a year ago, before they did release RHEL 9.
I cannot fathom how any version of RL 9 could have been without that patch.

the rpm -q --changelog systemd on my installation of RL9.1 show as last line:

* Wed Jan 27 2021 Fedora Release Engineering <releng@fedoraproject.org>
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild

My rl9.1 You have to grep for the term none as you have just posted the last line of the output

rpm -q --changelog systemd | grep none
- kernel-install: 90-loaderentry: error out on nonexistent initrds instead of swallowing them quietly (#2065061)
- udev/net-setup-link: change the default MACAddressPolicy to "none" (#2009237)
- core: decrease log level of messages about use of KillMode=none (#2013213)
- udev/net-setup-link: change the default MACAddressPolicy to "none" (#2009237)

What about rpm -qi systemd? (The version-release and build date.)

Follow the result that you asked for.

[$ rpm -q --changelog systemd | grep none
- kernel-install: 90-loaderentry: error out on nonexistent initrds instead of swallowing them quietly (#2065061)
- udev/net-setup-link: change the default MACAddressPolicy to "none" (#2009237)
- core: decrease log level of messages about use of KillMode=none (#2013213)
- udev/net-setup-link: change the default MACAddressPolicy to "none" (#2009237)
$ rpm -qi systemd
Name        : systemd
Version     : 250
Release     : 12.el9_1.1
Architecture: x86_64
Install Date: Thu 23 Feb 2023 10:56:14 AM CET
Group       : Unspecified
Size        : 13757156
License     : LGPLv2+ and MIT and GPLv2+
Signature   : RSA/SHA256, Mon 23 Jan 2023 09:45:04 PM CET, Key ID 702d426d350d275d
Source RPM  : systemd-250-12.el9_1.1.src.rpm
Build Date  : Mon 23 Jan 2023 09:05:35 PM CET
Build Host  : pb-cdb0ddf8-80e9-41fc-bced-364f19f64615-b-x86-64
Packager    : Rocky Linux Build System (Peridot) <releng@rockylinux.org>
Vendor      : Rocky Enterprise Software Foundation
URL         : https://www.freedesktop.org/wiki/Software/systemd
Summary     : System and Service Manager
Description :
systemd is a system and service manager that runs as PID 1 and starts
the rest of the system. It provides aggressive parallelization
capabilities, uses socket and D-Bus activation for starting services,
offers on-demand starting of daemons, keeps track of processes using
Linux control groups, maintains mount and automount points, and
implements an elaborate transactional dependency-based service control
logic. systemd supports SysV and LSB init scripts and works as a
replacement for sysvinit. Other parts of this package are a logging daemon,
utilities to control basic system configuration like the hostname,
date, locale, maintain a list of logged-in users, system accounts,
runtime directories and settings, and daemons to manage simple network
configuration, network time synchronization, log forwarding, and name
resolution.

Ok,

Just to make sure that we mean the same with “last”:

  • The changelog has latest entries “on top”, first and oldest at the “bottom”
  • rpm -q --changelog systemd | less is usually convenient way to peek what is new

Since your grep reveals the fix to (#2009237) to be in the package, the MACAddressPolicy should already be ‘none’ in your system and therefore not the cause of your issues.

Unfortunately after you helo I come to your same conclusion, but without the workaround that i find on github of systemd the bond on LACP are unusable and after apply no more errors in system logs files and the bond are working as expected.