systemd-networkd's dhcp4 client ignores local subnet routes

I haven't tested to confirm the broken behavior on jammy, but the patch looks straight forward. To help the process along, could you try to provide some simple steps to reproduce the bug on jammy?

Sure! Here is a quick test using a veth pair and dnsmasq:

ip link add veth0 up type veth peer name veth1
ip addr add 172.20.0.1/24 dev veth0
cat > /etc/netplan/60-veth1.yaml <<EOF
network:
  version: 2
  ethernets:
    veth1:
      dhcp4: true
EOF
dnsmasq -kq -C /dev/null -z -i veth0 -I lo -F 172.20.0.10,172.20.0.150 -O option:classless-static-route,169.254.0.0/24,0.0.0.0,169.254.1.0/24,172.20.0.2 &
netplan apply

Here is the resulting routing table on Jammy:

root@jammy:~# ip route
default via 10.199.96.88 dev ens2 proto dhcp src 10.199.96.89 metric 100
10.199.96.88 dev ens2 proto dhcp scope link src 10.199.96.89 metric 100
10.199.96.88/31 dev ens2 proto kernel scope link src 10.199.96.89 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.52 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.52 metric 100
172.20.0.1 dev veth1 proto dhcp scope link src 172.20.0.52 metric 100
172.20.0.2 dev veth1 proto dhcp scope link src 172.20.0.52 metric 100

As you can see, the route to 169.254.0.0/24 is missing. If I run the same on Focal, I get the following routing table:

root@focal:~# ip route
default via 10.76.140.48 dev ens2 proto dhcp src 10.76.140.49 metric 100
10.76.140.48 dev ens2 proto dhcp scope link src 10.76.140.49 metric 100
10.76.140.48/31 dev ens2 proto kernel scope link src 10.76.140.49
169.254.0.0/24 dev veth1 proto dhcp scope link src 172.20.0.53 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.53 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.53

Thanks!

Gentle ping? :)

I haven't had time to test yet, but I will look into this and include the patch in the next Jammy SRU if needed.

Thanks for the head's up!

I was able to confirm that this bug is present in Jammy, Kinetic, and Lunar. Focal does not have this bug.

Thanks for the test case!

Hello Tuetuopay, or anyone else affected,

Accepted systemd into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.2 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

Hello Tuetuopay, 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.8 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.

I confirmed this fix using systemd 249.11-0ubuntu3.8 from jammy-proposed:

root@jammy:~# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.8
  Candidate: 249.11-0ubuntu3.8
  Version table:
 *** 249.11-0ubuntu3.8 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.7 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        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@jammy:~# ip link add veth0 up type veth peer name veth1
root@jammy:~# ip addr add 172.20.0.1/24 dev veth0
root@jammy:~# cat > /etc/netplan/60-veth1.yaml <<EOF
network:
  version: 2
  ethernets:
    veth1:
      dhcp4: true
EOF
root@jammy:~# dnsmasq -kq -C /dev/null -z -i veth0 -I lo -F 172.20.0.10,172.20.0.150 -O option:classless-static-route,169.254.0.0/24,0.0.0.0,169.254.1.0/24,172.20.0.2 &
[1] 1113
root@jammy:~# netplan generate && netplan apply
root@jammy:~# ip route
default via 10.136.78.1 dev eth0 proto dhcp src 10.136.78.229 metric 100
10.136.78.0/24 dev eth0 proto kernel scope link src 10.136.78.229 metric 100
10.136.78.1 dev eth0 proto dhcp scope link src 10.136.78.229 metric 100
169.254.0.0/24 dev veth1 proto dhcp scope link src 172.20.0.125 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.125 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.125 metric 100
172.20.0.1 dev veth1 proto dhcp scope link src 172.20.0.125 metric 100
172.20.0.2 dev veth1 proto dhcp scope link src 172.20.0.125 metric 100

I confirmed the fix using systemd 251.4-1ubuntu7.2 from kinetic-proposed:

root@kinetic:~# apt-cache policy systemd
systemd:
  Installed: 251.4-1ubuntu7.2
  Candidate: 251.4-1ubuntu7.2
  Version table:
 *** 251.4-1ubuntu7.2 500
        500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     251.4-1ubuntu7.1 500
        500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 Packages
     251.4-1ubuntu7 500
        500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# ip link add veth0 up type veth peer name veth1
root@kinetic:~# ip addr add 172.20.0.1/24 dev veth0
root@kinetic:~# cat > /etc/netplan/60-veth1.yaml <<EOF
network:
  version: 2
  ethernets:
    veth1:
      dhcp4: true
EOF
root@kinetic:~# dnsmasq -kq -C /dev/null -z -i veth0 -I lo -F 172.20.0.10,172.20.0.150 -O option:classless-static-route,169.254.0.0/24,0.0.0.0,169.254.1.0/24,172.20.0.2 &
[1] 976
root@kinetic:~# netplan generate && netplan apply
root@kinetic:~# ip r
10.136.78.0/24 dev eth0 proto kernel scope link src 10.136.78.74 metric 100
169.254.0.0/24 dev veth1 proto dhcp scope link src 172.20.0.86 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.86 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.86 metric 100
172.20.0.1 dev veth1 proto dhcp scope link src 172.20.0.86 metric 100
172.20.0.2 dev veth1 proto dhcp scope link src 172.20.0.86 metric 100

This bug was fixed in the package systemd - 252.5-2ubuntu2

---------------
systemd (252.5-2ubuntu2) lunar; urgency=medium

  * network/dhcp4: accept local subnet routes from DHCP (LP: #2004478)
    File: debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b9aaaf37b8ca7c9febe5f0ebc4b82d0f895cbbd3
  * sd-netlink: skip test_rtnl_set_link_name when altnames are not supported.
    This has already been fixed upstream by a larger commit, so this patch
    can be dropped when we have a new enough upstream version.
    File: debian/patches/sd-netlink-skip-test_rtnl_set_link_name-when-altnames-are.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=195985ee5aa2cfdbbac178a07e5b43b83f0550d0

 -- Nick Rosbrook <email address hidden> Wed, 08 Mar 2023 12:51:51 -0500

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

openrazer/3.4.0+dfsg-1ubuntu1 (i386)
asterisk/1:18.14.0~dfsg+~cs6.12.40431414-1 (arm64)
network-manager/1.40.0-1ubuntu2 (amd64)
gvfs/1.50.2-2 (amd64)
freedombox/unknown (armhf)
php8.1/unknown (s390x)
lemonldap-ng/2.0.14+ds-1 (s390x, arm64)
udisks2/2.9.4-3 (amd64)
mandos/1.8.15-1 (arm64)
libsoup3/3.2.0-1 (ppc64el)
postgresql-common/242ubuntu1 (s390x)
nftables/1.0.5-1 (arm64)
mutter/43.0-1ubuntu4 (amd64)
ostree/2022.5-3 (s390x)
dropbear/2022.82-4 (armhf)
lighttpd/1.4.65-2ubuntu1.1 (s390x)
exim4/4.96-3ubuntu1.1 (ppc64el)
resource-agents/unknown (amd64)
liblinux-systemd-perl/1.201600-3build1 (s390x, arm64)
tinyssh/20190101-1ubuntu1 (s390x)
linux-lowlatency/5.19.0-1020.21 (amd64, arm64)
mediawiki/1:1.35.7-1 (s390x)
linux-oem-5.17/5.17.0-1003.3 (amd64)

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/kinetic/update_excuses.html#systemd

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

Thank you!

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

linux-intel-iotg/5.15.0-1027.32 (amd64)
linux-lowlatency/5.15.0-68.75 (arm64, amd64)
systemd/249.11-0ubuntu3.8 (arm64, ppc64el)
openrazer/3.2.0+dfsg-3 (i386)
multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x)
netplan.io/0.105-0ubuntu2~22.04.1 (amd64)
fwupd/1.7.9-1~22.04.1 (armhf)
udisks2/2.9.4-1ubuntu2 (amd64)
zfs-linux/unknown (s390x)
dbus/1.12.20-2ubuntu4.1 (s390x)
linux-ibm/5.15.0-1027.30 (amd64)
samba/unknown (s390x)
tang/11-1 (arm64)
gvfs/1.48.2-0ubuntu1 (arm64)
php8.1/unknown (s390x)
linux-nvidia/5.15.0-1018.18 (amd64)
csync2/2.0-25-gc0faaf9-1 (s390x)
tinyssh/20190101-1ubuntu1 (s390x)
mosquitto/2.0.11-1ubuntu1 (amd64)
casync/2+20201210-1build1 (ppc64el)
linux-gke/5.15.0-1029.34 (arm64, amd64)

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!

Hello Tuetuopay, or anyone else affected,

Accepted systemd into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.3 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

Hello Tuetuopay, 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.9 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.

I have re-confirmed the fix using systemd 249.11-0ubuntu3.9 from jammy-proposed:

root@jammy:~# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.9
  Version table:
 *** 249.11-0ubuntu3.9 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.7 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        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@jammy:~# ip link add veth0 up type veth peer name veth1
root@jammy:~# ip addr add 172.20.0.1/24 dev veth0
root@jammy:~# cat > /etc/netplan/60-veth1.yaml <<EOF
network:
  version: 2
  ethernets:
    veth1:
      dhcp4: true
EOF
root@jammy:~# dnsmasq -kq -C /dev/null -z -i veth0 -I lo -F 172.20.0.10,172.20.0.150 -O option:classless-static-route,169.254.0.0/24,0.0.0.0,169.254.1.0/24,172.20.0.2 &
[1] 1114
root@jammy:~# netplan generate && netplan apply
root@jammy:~# ip route
default via 10.136.78.1 dev eth0 proto dhcp src 10.136.78.118 metric 100
10.136.78.0/24 dev eth0 proto kernel scope link src 10.136.78.118 metric 100
10.136.78.1 dev eth0 proto dhcp scope link src 10.136.78.118 metric 100
169.254.0.0/24 dev veth1 proto dhcp scope link src 172.20.0.148 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.148 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.148 metric 100
172.20.0.1 dev veth1 proto dhcp scope link src 172.20.0.148 metric 100
172.20.0.2 dev veth1 proto dhcp scope link src 172.20.0.148 metric 100

I have re-confirmed the fix using systemd 251.4-1ubuntu7.3 from kinetic-proposed:

root@kinetic:~# apt-cache policy systemd
systemd:
  Installed: 251.4-1ubuntu7.3
  Candidate: 251.4-1ubuntu7.3
  Version table:
 *** 251.4-1ubuntu7.3 500
        500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     251.4-1ubuntu7.1 500
        500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 Packages
     251.4-1ubuntu7 500
        500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# ip link add veth0 up type veth peer name veth1
root@kinetic:~# ip addr add 172.20.0.1/24 dev veth0
root@kinetic:~# cat > /etc/netplan/60-veth1.yaml <<EOF
network:
  version: 2
  ethernets:
    veth1:
      dhcp4: true
EOF
root@kinetic:~# dnsmasq -kq -C /dev/null -z -i veth0 -I lo -F 172.20.0.10,172.20.0.150 -O option:classless-static-route,169.254.0.0/24,0.0.0.0,169.254.1.0/24,172.20.0.2 &
[1] 1077
root@kinetic:~# netplan generate && netplan apply
root@kinetic:~# ip route
10.136.78.0/24 dev eth0 proto kernel scope link src 10.136.78.181 metric 100
169.254.0.0/24 dev veth1 proto dhcp scope link src 172.20.0.89 metric 100
169.254.1.0/24 via 172.20.0.2 dev veth1 proto dhcp src 172.20.0.89 metric 100
172.20.0.0/24 dev veth0 proto kernel scope link src 172.20.0.1
172.20.0.0/24 dev veth1 proto kernel scope link src 172.20.0.89 metric 100
172.20.0.1 dev veth1 proto dhcp scope link src 172.20.0.89 metric 100
172.20.0.2 dev veth1 proto dhcp scope link src 172.20.0.89 metric 100

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

casync/2+20201210-1build1 (ppc64el)
dpdk/21.11.3-0ubuntu0.22.04.1 (arm64)
fwupd/1.7.9-1~22.04.1 (armhf)
init-system-helpers/unknown (s390x)
initramfs-tools/0.140ubuntu13.1 (amd64)
libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (s390x)
libsoup3/3.0.7-0ubuntu1 (s390x)
libvirt/8.0.0-1ubuntu7.4 (s390x)
linux-lowlatency-hwe-5.19/5.19.0-1021.22~22.04.1 (amd64, arm64)
linux-nvidia/5.15.0-1018.18 (amd64)
mutter/42.5-0ubuntu1 (amd64)
netplan.io/0.105-0ubuntu2~22.04.3 (arm64, s390x)
network-manager/1.36.6-0ubuntu2 (s390x)
nextepc/unknown (s390x)
open-iscsi/2.1.5-1ubuntu1 (s390x)
openrazer/3.2.0+dfsg-3 (i386)
pdns-recursor/unknown (s390x)
postgresql-14/unknown (s390x)
pystemd/0.7.0-5build1 (s390x)
samba/unknown (s390x)
strongswan/unknown (s390x)
systemd/249.11-0ubuntu3.9 (s390x)
umockdev/0.17.7-1 (s390x)
zfs-linux/unknown (s390x)

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!

All autopkgtests for the newly accepted systemd (251.4-1ubuntu7.3) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

csync2/2.0-42-g83b3644-1 (s390x)
dpdk/21.11.3-0ubuntu0.22.10.1 (arm64)
initramfs-tools/0.140ubuntu17 (s390x)
lemonldap-ng/2.0.14+ds-1 (s390x)
liblinux-systemd-perl/unknown (s390x)
libsoup3/3.2.0-1 (armhf, s390x)
libvirt/unknown (s390x)
libvirt-dbus/unknown (s390x)
lighttpd/1.4.65-2ubuntu1.1 (s390x)
linux-lowlatency/5.19.0-1021.22 (amd64, arm64)
mutter/43.0-1ubuntu4 (amd64)
netplan.io/0.105-0ubuntu2.2 (s390x)
openrazer/3.4.0+dfsg-1ubuntu1 (i386)
openvpn/unknown (s390x)
procps/unknown (s390x)
prometheus-postfix-exporter/unknown (s390x)
remctl/3.18-1build1 (s390x)
resource-agents/unknown (s390x)
snapd/unknown (s390x)
tinyssh/20190101-1ubuntu1 (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/kinetic/update_excuses.html#systemd

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

Thank you!

This bug was fixed in the package systemd - 251.4-1ubuntu7.3

---------------
systemd (251.4-1ubuntu7.3) kinetic; urgency=medium

  * udev: gracefully handle rename failures (LP: #2002445)
    Files:
    - debian/patches/lp2002445/core-device-ignore-failed-uevents.patch
    - debian/patches/lp2002445/sd-device-introduce-device_get_property_int.patch
    - debian/patches/lp2002445/sd-device-make-device_set_syspath-clear-sysname-and-sysnu.patch
    - debian/patches/lp2002445/udev-restore-syspath-and-properties-on-failure.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=deb435fbb84fde1fd39da47231a7473fc2a412e8

systemd (251.4-1ubuntu7.2) kinetic; urgency=medium

  * network/dhcp4: accept local subnet routes from DHCP (LP: #2004478)
    File: debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=751bac59b405025964d76c4ef8e0603457a605af
  * udev: avoid NIC renaming race with kernel (LP: #2002445)
    Files:
    - debian/patches/lp2002445/sd-netlink-add-a-test-for-rtnl_set_link_name.patch
    - debian/patches/lp2002445/sd-netlink-do-not-swap-old-name-and-alternative-name.patch
    - debian/patches/lp2002445/sd-netlink-restore-altname-on-error-in-rtnl_set_link_name.patch
    - debian/patches/lp2002445/udev-attempt-device-rename-even-if-interface-is-up.patch
    - debian/patches/lp2002445/udev-net-allow-new-link-name-as-an-altname-before-renamin.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ffb1e85fdd3f0fe9b158b28a95cfa6d241fcbe70

 -- Nick Rosbrook <email address hidden> Mon, 20 Mar 2023 10:25:23 -0400

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.

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

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

  * udev: gracefully handle rename failures (LP: #2002445)
    Files:
    - debian/patches/lp2002445/core-device-ignore-failed-uevents.patch
    - debian/patches/lp2002445/sd-device-introduce-device_get_property_int.patch
    - debian/patches/lp2002445/sd-device-make-device_set_syspath-clear-sysname-and-sysnu.patch
    - debian/patches/lp2002445/udev-restore-syspath-and-properties-on-failure.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a7ad4a9fc708500c61e3b8127f112d8c90049b2c

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

  * network/dhcp4: accept local subnet routes from DHCP (LP: #2004478)
    File: debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=96928d5f45ebbfe682b47e842d63506fa0ac9583
  * udev: avoid NIC renaming race with kernel (LP: #2002445)
    Files:
    - debian/patches/lp2002445/sd-netlink-add-a-test-for-rtnl_set_link_name.patch
    - debian/patches/lp2002445/sd-netlink-do-not-swap-old-name-and-alternative-name.patch
    - debian/patches/lp2002445/sd-netlink-restore-altname-on-error-in-rtnl_set_link_name.patch
    - debian/patches/lp2002445/udev-attempt-device-rename-even-if-interface-is-up.patch
    - debian/patches/lp2002445/udev-net-allow-new-link-name-as-an-altname-before-renamin.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=20dc4d51a340669c26c446c23b5a84516e82ea74
  * network: create stacked netdevs after the underlying link is (LP: #2000880)
    File: debian/patches/lp2000880-network-create-stacked-netdevs-after-the-underlying-link-.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab620e709f3f62eda86af26fd66c00d6e5165a25
  * Enable /dev/sgx_vepc access for the group 'sgx' (LP: #2009502)
    File: debian/patches/lp2009502-Enable-dev-sgx_vepc-access-for-the-group-sgx.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=434480ae4059a16ccbde9613be0c26ff1983cc3a

 -- Nick Rosbrook <email address hidden> Mon, 20 Mar 2023 10:32:08 -0400

Thank you so much to everyone involved :)