networkd: classless routes served by DHCP are created incorrectly

[Pedro Lopes]

[Impact]

Classless static routes served by DHCP are ignored by networkd in some cases. Specifically, the gateway is not being set for routes whenever the route destination is in the assigned network. This is a regression in behavior since Focal.

[Test Plan]

This is basically taken from systemd-networkd-tests.py. Using a veth pair, setup dnsmasq to serve the problematic routes:

$ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
[Match]
Name=veth-peer

[Network]
IPv6AcceptRA=no
Address=2600::1/0
Address=192.168.5.1/24
EOF

$ cat > /etc/systemd/network/25-test.network << EOF
[Match]
Name=veth99

[Network]
DHCP=ipv4
IPv6AcceptRA=false

[DHCPv4]
UseRoutes=yes
EOF

$ cat > /etc/systemd/network/25-veth.netdev << EOF
[NetDev]
Name=veth99
Kind=veth
MACAddress=12:34:56:78:9a:bc

[Peer]
Name=veth-peer
MACAddress=12:34:56:78:9a:bd
EOF

$ mkdir -p /etc/systemd/system/systemd-networkd.service.d/
$ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF

$ systemctl daemon-reload
$ systemctl restart systemd-networkd
$ mkdir -p /run/networkd-ci
$ dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null --bind-interfaces --interface=veth-peer --dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra --dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m --dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 --no-resolv --dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5 &

$ systemctl restart systemd-networkd

On an affected machine, the route to 192.168.5.64 on veth99 will be missing it's gateway address:

$ ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 proto dhcp scope link src 192.168.5.181 metric 1024

And, there will be a log message explaining that this was done intentionally:

$ journalctl -u systemd-networkd --grep="veth99.*assigned network"
Aug 03 16:58:49 mantic2 systemd-networkd[1418]: veth99: DHCP: requested route destination 192.168.5.64/26 is in the assigned network 192.168.5.0/24, ignoring gateway address 192.168.5.5

On a fixed machine, the route for to 192.168.5.64 will correctly have its gateway configured:

$ ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024

[Where problems could occur]

The patch is in the DHCPv4 client code for handling routes from the DHCP server. It adds a flag, force_use_gw, to an internal function that essentially overrides the "ignore" behavior whenever classless static routes have been given. If we saw regressions, it would be related to creation of static routes handed down by DHCPv4 servers.

[Original Description]

After upgrading 20.04 systems to 22.04, the classless routes served via DHCP are not being registered correctly - they are missing the gateway address.

Expected routes - these are taken from a 20.04 system on the same network:

$ ip route
default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

Actual routes - these are the routes created in one of the affected 22.04 systems:

$ ip route
default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" gateway address, and therefore don't work.
(For some reason there are also static routes created for DNS server (8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but harmless.)

Both the working and non-working systems are being managed by netplan. The non-working system has a bonded interface but I have checked that is not the cause of the problem - using a physical interface directly has the same result.

I have attached the files /etc/netplan/00-installer-config.yaml and /run/systemd/network/10-netplan-bond0.network of the affected system.

Affected system:
Ubuntu version: Ubuntu 22.04.2 LTS
systemd version: 249.11-0ubuntu3.6

Older system not affected:
Ubuntu version: Ubuntu 20.04.5 LTS
systemd version: 245.4-4ubuntu3.19

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sylvain Guglielmi (g-ugli)]

I have the same issue.

I may be wrong, but it seem to me that it's related to the following DHCP options :
DHCP option 1 : [SubnetMask]
DHCP option 121 : classless static route [DestCIDR] [Gateway]
When DestCIDR is within the subnet, the gateway is dropped by systemd-networkd : the route is added, without gateway.

@Pedro Lopes : does this match your occurrence of the issue.

Note that dhclient does not have this bug : running dhclient adds the correct routes.

Unfortunately for me, the concerned machines are in production. So further testing is not easy.

[Pedro Lopes (paol)]

Yes I can confirm the classless routes we are trying to serve are under the main subnet:

10.0.0.0/8 dev enp24s0
10.88.88.0/24 via 10.10.1.2 dev enp24s0
10.96.0.0/11 via 10.10.1.2 dev enp24s0

[Nick Rosbrook (enr0n)]

Hi Pedro,

Can you please try this with the latest version of systemd? We have 249.11-0ubuntu3.9 which has a patch for a similar sounding bug (I don't *think* it's the same thing, but just to be sure).

Assuming that does not resolve the issue, can you please provide debug-level logs from systemd-networkd during a span where the routes would be created? You can enable debug logging by doing:

$ mkdir -p /etc/systemd/system/systemd-networkd.service.d
$ cat > /etc/systemd/system/systemd-networkd.service.d << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
$ systemctl daemon-reload
$ systemctl restart systemd-networkd

Then grab some logs from an appropriate timespan. I think networkctl forcerenew should do the trick:

$ networkctl forcerenew
$ journalctl -u systemd-networkd --since "5min ago" > logs.txt

[Pedro Lopes (paol)]

Here is the requested log. The sequence of operations was:

sudo systemctl restart systemd-networkd
sudo networkctl forcerenew bond0

Sylvain's diagnostic seems to have hit the nail on the head. I see the following messages in the log:

bond0: DHCP: requested route destination 10.88.88.0/24 is in the assigned network 10.0.0.0/8, ignoring gateway address 10.10.1.2
bond0: DHCP: requested route destination 10.96.0.0/11 is in the assigned network 10.0.0.0/8, ignoring gateway address 10.10.1.2

[Pedro Lopes (paol)]

I forgot to say, the above was after updating systemd to 249.11-0ubuntu3.9

[Łukasz Zemczak (sil2100)]

Hello Pedro, or anyone else affected,

Accepted systemd into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/252.5-2ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Pedro, or anyone else affected,

Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.10) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.4.10 (armhf)
casync/2+20201210-1build1 (ppc64el)
comitup/1.15-1 (armhf)
dbus/1.12.20-2ubuntu4.1 (armhf)
initramfs-tools/0.140ubuntu13.4 (s390x)
linux-azure-5.19/5.19.0-1027.30~22.04.2 (arm64)
linux-gcp-6.2/6.2.0-1011.11~22.04.3 (arm64)
linux-lowlatency/5.15.0-83.92 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1030.30 (arm64)
linux-nvidia-tegra/5.15.0-1016.16 (arm64)
linux-oracle-5.19/5.19.0-1027.30 (arm64)
mkosi/unknown (s390x)
munin/2.0.57-1ubuntu2 (armhf)
netplan.io/0.105-0ubuntu2~22.04.3 (arm64)
prometheus-postfix-exporter/unknown (s390x)
samba/2:4.15.13+dfsg-0ubuntu1.4 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (252.5-2ubuntu3.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.6.0ubuntu0.1 (armhf)
clutter-1.0/unknown (amd64)
corosync/3.1.7-1ubuntu1 (i386)
cryptsetup/unknown (s390x)
libreswan/unknown (s390x)
libsdl2/unknown (s390x)
linux-lowlatency/6.2.0-1012.12 (arm64)
mutter/44.3-0ubuntu1 (amd64)
netplan.io/0.106-0ubuntu3 (arm64)
samba/2:4.17.7+dfsg-1ubuntu2.2 (arm64)
stunnel4/3:5.68-2 (i386)
stunnel4/unknown (s390x)
systemd-bootchart/234-2 (amd64)
ubuntu-drivers-common/1:0.9.7.1.1 (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Nick Rosbrook (enr0n)]

I have verified the fix on Lunar using systemd 252.5-2ubuntu3.1 from lunar-proposed:

root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
        500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     252.5-2ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
[Match]
Name=veth-peer

[Network]
IPv6AcceptRA=no
Address=2600::1/0
Address=192.168.5.1/24
EOF
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/25-test.network << EOF
[Match]
Name=veth99

[Network]
DHCP=ipv4
IPv6AcceptRA=false

[DHCPv4]
UseRoutes=yes
EOF
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/network/25-veth.netdev << EOF
[NetDev]
Name=veth99
Kind=veth
MACAddress=12:34:56:78:9a:bc

[Peer]
Name=veth-peer
MACAddress=12:34:56:78:9a:bd
EOF
root@clean-lunar-amd64:/home/nr# mkdir -p /etc/systemd/system/systemd-networkd.service.d/
root@clean-lunar-amd64:/home/nr# cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
root@clean-lunar-amd64:/home/nr# systemctl daemon-reload
root@clean-lunar-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-lunar-amd64:/home/nr# mkdir -p /run/networkd-ci
root@clean-lunar-amd64:/home/nr# dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null --bind-interfaces --interface=veth-peer --dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra --dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m --dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 --no-resolv --dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5 &
[1] 2573
root@clean-lunar-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-lunar-amd64:/home/nr# ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024
root@clean-lunar-amd64:/home/nr# journalctl -u systemd-networkd --grep="veth99.*assigned network"
-- No entries --
root@clean-lunar-amd64:/home/nr#

[Nick Rosbrook (enr0n)]

I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from jammy-proposed:

root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.10
  Candidate: 249.11-0ubuntu3.10
  Version table:
 *** 249.11-0ubuntu3.10 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.9 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
     249.11-0ubuntu3.7 500
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     249.11-0ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
[Match]
Name=veth-peer

[Network]
IPv6AcceptRA=no
Address=2600::1/0
Address=192.168.5.1/24
EOF
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/25-test.network << EOF
[Match]
Name=veth99

[Network]
DHCP=ipv4
IPv6AcceptRA=false

[DHCPv4]
UseRoutes=yes
EOF
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/network/25-veth.netdev << EOF
[NetDev]
Name=veth99
Kind=veth
MACAddress=12:34:56:78:9a:bc

[Peer]
Name=veth-peer
MACAddress=12:34:56:78:9a:bd
EOF
root@clean-jammy-amd64:/home/nr# mkdir -p /etc/systemd/system/systemd-networkd.service.d/
root@clean-jammy-amd64:/home/nr# cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
root@clean-jammy-amd64:/home/nr# systemctl daemon-reload
root@clean-jammy-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-jammy-amd64:/home/nr# mkdir -p /run/networkd-ci
root@clean-jammy-amd64:/home/nr# dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null --bind-interfaces --interface=veth-peer --dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra --dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m --dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 --no-resolv --dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5 &
[1] 1418
root@clean-jammy-amd64:/home/nr#
[1]+ Done dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log --log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid --conf-file=/dev/null --bind-interfaces --interface=veth-peer --dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra --dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m --dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 --no-resolv --dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
root@clean-jammy-amd64:/home/nr#
root@clean-jammy-amd64:/home/nr#
root@clean-jammy-amd64:/home/nr#
root@clean-jammy-amd64:/home/nr# systemctl restart systemd-networkd
root@clean-jammy-amd64:/home/nr# ip r show dev veth99 192.168.5.64/26
192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024
root@clean-...

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 253.5-1ubuntu4

---------------
systemd (253.5-1ubuntu4) mantic; urgency=medium

  * Revert "Drop Provides: time-daemon for bin:systemd-timesyncd"
    File: debian/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e88d9f0241a307a3c1b4bcaf4bf29799d984aa3c

 -- Nick Rosbrook <email address hidden> Fri, 25 Aug 2023 16:36:26 -0400

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 252.5-2ubuntu3.1

---------------
systemd (252.5-2ubuntu3.1) lunar; urgency=medium

  * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
    File: debian/tests/tests-in-lxd
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2a443ddd5b67596647e463eee64d58c3c71bbf08
  * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180)
    File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=064c7c00aa133b697ab3c0082b825e2f197f91cc
  * core: reorder systemd arguments on reexec (LP: #2013543)
    File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=45541ccbc16ed30b6a120cda7401f69cce164d54
  * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743)
    Files:
    - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch
    - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ddea3bcbca3421299b13cfe897157cfbf9f0f06d
  * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543
    File: debian/systemd.postinst
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e1a08bb427e19ced6c16f054ebdee43ccbc9c528
  * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218)
    File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8235427fd8859ee393a08d425e1a52e1ebcbe2f1
  * sd-bus: bus_message_type_from_string is not pure (LP: #2031683)
    File: debian/patches/lp2031683-sd-bus-bus_message_type_from_string-is-not-pure.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2d65b6c74864976a2bb42c884baf75d1674215fc

 -- Nick Rosbrook <email address hidden> Fri, 18 Aug 2023 14:15:03 -0400

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 249.11-0ubuntu3.10

---------------
systemd (249.11-0ubuntu3.10) jammy; urgency=medium

  [ Nick Rosbrook ]
  * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
    File: debian/tests/tests-in-lxd
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313
  * pstore: only try to load efi_pstore module (LP: #2023462)
    File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89
  * shutdown: get only active md arrays. (LP: #2025563)
    File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3
  * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180)
    File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278
  * core: reorder systemd arguments on reexec (LP: #2013543)
    File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280
  * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743)
    Files:
    - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch
    - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0
  * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218)
    File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588
  * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543
    File: debian/systemd.postinst
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7
  * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275)
    Files:
    - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch
    - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch
    - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch
    - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3

  [ Dan Streetman ]
  * Fix machinectl pull-tar and import-tar (LP: #1977630)
    Author: Dan Streetman
    File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+sourc...

[Steve Langasek (vorlon)]

The release of this SRU has been rolled back in jammy because of bug #2035406 which appears to be a regression introduced in the new version of systemd.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 249.11-0ubuntu3.10

---------------
systemd (249.11-0ubuntu3.10) jammy; urgency=medium

  [ Nick Rosbrook ]
  * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
    File: debian/tests/tests-in-lxd
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313
  * pstore: only try to load efi_pstore module (LP: #2023462)
    File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89
  * shutdown: get only active md arrays. (LP: #2025563)
    File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3
  * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180)
    File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278
  * core: reorder systemd arguments on reexec (LP: #2013543)
    File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280
  * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743)
    Files:
    - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch
    - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0
  * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218)
    File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588
  * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543
    File: debian/systemd.postinst
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7
  * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275)
    Files:
    - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch
    - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch
    - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch
    - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3

  [ Dan Streetman ]
  * Fix machinectl pull-tar and import-tar (LP: #1977630)
    Author: Dan Streetman
    File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+sourc...