PTP device symlink missing after running udevadm trigger command

[Chengen Du]

[Impact]
PTP device symlink creation rules are executed only when the udev action is 'add'.
If the rules are reloaded and the udevadm trigger command is run to reapply changes, the symlink may be deleted.
This can prevent the chronyd service from restarting properly.

[Fix]
Upstream has a patch to fix this issue.

commit 6bd12be3fa7761f190e17efdbdbff4440da7528b
Author: Chengen Du <email address hidden>
CommitDate: Thu Aug 15 15:38:46 2024 +0900

    udev: Handle PTP device symlink properly on udev action 'change'

    PTP device symlink creation rules are currently executed only when the
    udev action is 'add'. If a user reloads the rules and runs the udevadm
    trigger command to reapply changes, the symlink may be deleted, which
    can prevent the chronyd service from restarting properly.

    Signed-off-by: Chengen Du <email address hidden>

[Test Plan]
1. Create a VM with a PTP device.
2. Verify that the PTP device symlink is present:
> ll /dev/ptp*
crw------- 1 root root 246, 0 Oct 14 02:26 /dev/ptp0
lrwxrwxrwx 1 root root 4 Oct 14 02:26 /dev/ptp_hyperv -> ptp0
2. Run the `udevadm trigger` command.
3. Verify again that the PTP device symlink is still present.

[Where problems could occur]
The patch allows PTP device symlink creation rules to be executed when the udev action is 'change'.
This update primarily affects services that rely on the PTP device symlink, such as chronyd.

[Chengen Du (chengendu)]

Debdiff for Focal

[Chengen Du (chengendu)]

Debdiff for Jammy

[Chengen Du (chengendu)]

Debdiff for Noble

[Chengen Du (chengendu)]

Debdiff for Oracular

[Heitor Alves de Siqueira (halves)]

Thanks for the patch, Chengen!

Debdiff for Oracular looks good, but we need someone to sponsor that one first (thus I'm subscribing ~ubuntu-sponsors). Once -devel is fixed, we can look into getting the stable series merged.

[Nick Rosbrook (enr0n)]

This patch is in v256.5, which I prepared and uploaded today.

[Nick Rosbrook (enr0n)]

I am tracking this for future SRUs, so unsubscribing sponsors.

[Nick Rosbrook (enr0n)]

A few questions regarding the test plan:

> 1. Create a VM on Azure.

Is chrony the default NTP server on Azure images? It seems we could test this without Azure if so. Is there a specific chrony.conf needed to see this issue?

> 2. Run the `udevadm trigger` command.
> 3. Restart the chronyd service by running `systemctl restart chronyd`.
> 4. Verify that the service starts normally by running `systemctl status chronyd`.

Can you please provide an example of what this failure actually looks like in practice? I am able to reproduce the removal of /dev/ptp_kvm symlink, but not a chrony failure.

I suppose we don't *need* chrony in the test plan, since we can test the symlink itself. But, if you want chrony to be tested, please provide some clarification.

[Chengen Du (chengendu)]

Hi, Chrony is the default NTP service on Azure images, and the following error occurs when the PTP device symlink is missing:
Oct 14 02:38:42 test-jammy-no-pro systemd[1]: Starting chrony, an NTP client/server...
Oct 14 02:38:42 test-jammy-no-pro chronyd[3200]: chronyd version 4.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +I
PV6 -DEBUG)
Oct 14 02:38:42 test-jammy-no-pro chronyd[3200]: Could not open /dev/ptp_hyperv : No such file or directory
Oct 14 02:38:42 test-jammy-no-pro chronyd[3200]: Fatal error : Could not open PHC
Oct 14 02:38:42 test-jammy-no-pro chronyd-starter.sh[3198]: Could not open PHC
Oct 14 02:38:42 test-jammy-no-pro systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE
Oct 14 02:38:42 test-jammy-no-pro systemd[1]: chrony.service: Failed with result 'exit-code'.
Oct 14 02:38:42 test-jammy-no-pro systemd[1]: Failed to start chrony, an NTP client/server.

I agree with you that Chrony doesn't need to be included in the test plan, as it's simply a result of the missing PTP device symlink.
I've updated the test plan accordingly.

[Timo Aaltonen (tjaalton)]

Hello Chengen, or anyone else affected,

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

[Timo Aaltonen (tjaalton)]

Hello Chengen, 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.13 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.

[Chengen Du (chengendu)]

Both -proposed versions in Jammy and Noble have been tested and confirmed to work without any issues.

[Jammy]
root@jammy-ptp:~# apt policy udev
udev:
  Installed: 249.11-0ubuntu3.13
  Candidate: 249.11-0ubuntu3.13
  Version table:
 *** 249.11-0ubuntu3.13 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.12 500
        500 http://tw.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://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@jammy-ptp:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Nov 18 03:50 /dev/ptp0
lrwxrwxrwx 1 root root 4 Nov 18 03:50 /dev/ptp_kvm -> ptp0
root@jammy-ptp:~# udevadm trigger
root@jammy-ptp:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Nov 18 03:51 /dev/ptp0
lrwxrwxrwx 1 root root 4 Nov 18 03:51 /dev/ptp_kvm -> ptp0

[Noble]
root@noble-ptp:~# apt policy udev
udev:
  Installed: 255.4-1ubuntu8.5
  Candidate: 255.4-1ubuntu8.5
  Version table:
 *** 255.4-1ubuntu8.5 100
        100 http://tw.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     255.4-1ubuntu8.4 500
        500 http://tw.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
     255.4-1ubuntu8 500
        500 http://tw.archive.ubuntu.com/ubuntu noble/main amd64 Packages
root@noble-ptp:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Nov 18 05:09 /dev/ptp0
lrwxrwxrwx 1 root root 4 Nov 18 05:09 /dev/ptp_kvm -> ptp0
root@noble-ptp:~# udevadm trigger
root@noble-ptp:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Nov 18 05:09 /dev/ptp0
lrwxrwxrwx 1 root root 4 Nov 18 05:09 /dev/ptp_kvm -> ptp0

[Mauricio Faria de Oliveira (mfo)]

Hello Chengen, 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.14 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.

[Chengen Du (chengendu)]

The -proposed version in Jammy has been thoroughly tested and confirmed to function without any issues.

[Jammy]
root@ptp-jammy:~# apt policy udev
udev:
  Installed: 249.11-0ubuntu3.14
  Candidate: 249.11-0ubuntu3.14
  Version table:
 *** 249.11-0ubuntu3.14 100
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.13 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
     249.11-0ubuntu3.12 500
        500 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
     249.11-0ubuntu3.7 500
        500 http://azure.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     249.11-0ubuntu3 500
        500 http://azure.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@ptp-jammy:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Dec 17 00:54 /dev/ptp0
crw------- 1 root root 246, 1 Dec 17 00:54 /dev/ptp1
lrwxrwxrwx 1 root root 4 Dec 17 00:54 /dev/ptp_hyperv -> ptp0
root@ptp-jammy:~# udevadm trigger
root@ptp-jammy:~# ll /dev/ptp*
crw------- 1 root root 246, 0 Dec 17 00:56 /dev/ptp0
crw------- 1 root root 246, 1 Dec 17 00:56 /dev/ptp1
lrwxrwxrwx 1 root root 4 Dec 17 00:56 /dev/ptp_hyperv -> ptp0

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

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

docker.io-app/unknown (ppc64el)
dovecot/1:2.3.16+dfsg1-3ubuntu2.4 (s390x)
dpdk/unknown (ppc64el)
gpsd/unknown (ppc64el)
gvfs/unknown (ppc64el)
haproxy/2.4.24-0ubuntu0.22.04.1 (ppc64el)
indicator-session/17.3.20+21.10.20210613.1-0ubuntu1 (ppc64el)
init-system-helpers/unknown (ppc64el)
knot-resolver/unknown (ppc64el)
libqb/unknown (ppc64el)
linux-azure-6.8/6.8.0-1019.22~22.04.1 (arm64)
linux-gcp-6.8/6.8.0-1020.22~22.04.1 (arm64)
linux-gke/5.15.0-1070.76 (arm64)
linux-hwe-6.5/6.5.0-45.45~22.04.1 (arm64)
linux-hwe-6.8/6.8.0-50.51~22.04.1 (amd64)
linux-ibm-6.8/6.8.0-1017.17~22.04.1 (amd64)
linux-lowlatency-hwe-6.5/6.5.0-45.45.1~22.04.1 (amd64, arm64)
linux-lowlatency-hwe-6.8/6.8.0-50.51.1~22.04.1 (arm64)
linux-nvidia-6.5/6.5.0-1024.25 (arm64)
linux-nvidia-6.8/6.8.0-1020.22~22.04.1 (arm64)
linux-nvidia-tegra/5.15.0-1030.30 (arm64)
linux-oracle-6.5/6.5.0-1027.27~22.04.1 (amd64)
zfs-linux/2.1.5-1ubuntu6~22.04.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!

[Chengen Du (chengendu)]

@enr0n It seems that none of the regressions are related to this patch. Would it be possible to retrigger the autopkgtest?

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

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.5) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

linux-nvidia/6.8.0-1020.22 (arm64)
linux-oem-6.8/unknown (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/noble/update_excuses.html#systemd

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

Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 255.4-1ubuntu8.5

---------------
systemd (255.4-1ubuntu8.5) noble; urgency=medium

  [ Chengen Du ]
  * udev: Handle PTP device symlink properly on udev action 'change'
    (LP: #2077779)

  [ Nick Rosbrook ]
  * core/exec-invoke: Fix missing arguments for PR_SET_MEMORY_MERGE call
    (LP: #2081192)

 -- Nick Rosbrook <email address hidden> Thu, 17 Oct 2024 13:15:16 -0400

[Andreas Hasenack (ahasenack)]

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.

[Chris Halse Rogers (raof)]

An upload of systemd to jammy-proposed has been rejected from the upload queue for the following reason: "Prerm is missing the #DEBHELPER# substitution that would include any other scripts generated by debhelper. This doesn't seem intentional. Also, should this wait for the existing systemd in -proposed to be verot entangle this bug with the others? Feel free to reach out with any questions/answers :)".

[Andreas Hasenack (ahasenack)]

Hello Chengen, 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.15 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.15) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

apt/unknown (armhf)
bolt/unknown (armhf)
casync/unknown (armhf)
debspawn/0.5.2-1 (ppc64el)
flatpak/1.12.7-1ubuntu0.1 (amd64)
fluidsynth/unknown (armhf)
freedombox/unknown (armhf)
freeipa/unknown (armhf)
freeradius/unknown (armhf)
fwupd/unknown (armhf)
gamemode/unknown (armhf)
gdm3/unknown (armhf)
golang-github-coreos-go-systemd/unknown (armhf)
gpsd/unknown (armhf)
gvfs/unknown (armhf)
haproxy/unknown (armhf)
hwloc/unknown (armhf)
icinga2/unknown (armhf)
libsoup3/3.0.7-0ubuntu1 (amd64)
linux-gcp-6.8/6.8.0-1024.26~22.04.1 (amd64)
linux-gke/5.15.0-1077.83 (amd64)
linux-hwe-6.5/6.5.0-45.45~22.04.1 (amd64)
linux-hwe-6.5/unknown (armhf)
linux-hwe-6.8/unknown (armhf)
linux-lowlatency/5.15.0-135.146 (amd64)
linux-lowlatency-hwe-6.5/6.5.0-45.45.1~22.04.1 (amd64)
mir/unknown (armhf)
mkosi/unknown (armhf)
monitoring-plugins-systemd/unknown (armhf)
mpd/unknown (armhf)
multipath-tools/unknown (armhf)
munin/unknown (armhf)
mutter/unknown (armhf)
nagios-tang/unknown (armhf)
openssh/1:8.9p1-3ubuntu0.11 (amd64)
policykit-1/unknown (armhf)
polkit-qt-1/unknown (armhf)
postgresql-14/unknown (armhf)
prometheus-postgres-exporter/unknown (armhf)
prometheus-squid-exporter/unknown (armhf)
pulseaudio/unknown (armhf)
python-dbusmock/unknown (armhf)
python-systemd/unknown (armhf)
python-uinput/unknown (armhf)
pyudev/unknown (armhf)
qlcplus/unknown (armhf)
swupdate/2021.11-1 (amd64)
systemd-bootchart/unknown (armhf)
tgt/1:1.0.80-1ubuntu2 (amd64)
tpm2-abrmd/unknown (armhf)
tpm2-pkcs11/unknown (armhf)
ubuntu-drivers-common/unknown (armhf)
udisks2/unknown (armhf)
util-linux/unknown (armhf)
vlc/unknown (armhf)

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!

[Nick Rosbrook (enr0n)]

I re-verified the fix using systemd/udev 249.11-0ubuntu3.15 from jammy-proposed:

ubuntu@ubuntu:~$ ls -alh /dev/ptp_kvm
lrwxrwxrwx 1 root root 4 Feb 28 15:15 /dev/ptp_kvm -> ptp0
ubuntu@ubuntu:~$ sudo udevadm trigger
ubuntu@ubuntu:~$ ls -alh /dev/ptp_kvm
ls: cannot access '/dev/ptp_kvm': No such file or directory
ubuntu@ubuntu:~$ apt policy udev
udev:
  Installed: 249.11-0ubuntu3.12
  Candidate: 249.11-0ubuntu3.12
  Version table:
 *** 249.11-0ubuntu3.12 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     249.11-0ubuntu3.7 500
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     249.11-0ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# cat > /etc/apt/sources.list.d/proposed.list << EOF
deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main universe
EOF
root@ubuntu:/home/ubuntu# cat <<EOF >/etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=jammy-proposed
Pin-Priority: 400
EOF
root@ubuntu:/home/ubuntu# apt update && apt install -y -t jammy-proposed systemd udev
Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu jammy-proposed InRelease [279 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages [364 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages [98.8 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy-proposed/main Translation-en [75.1 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 DEP-11 Metadata [5,720 B]
Get:10 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 48x48 Icons [1,625 B]
Get:11 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 64x64 Icons [2,436 B]
Get:12 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 64x64@2 Icons [29 B]
Get:13 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 c-n-f Metadata [1,740 B]
Get:14 http://archive.ubuntu.com/ubuntu jammy-proposed/universe i386 Packages [32.4 kB]
Get:15 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages [85.1 kB]
Get:16 http://archive.ubuntu.com/ubuntu jammy-proposed/universe Translation-en [30.0 kB]
Get:17 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 DEP-11 Metadata [1,448 B]
Get:18 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 48x48 Icons [4,982 B]
Get:19 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 64x64 Icons [8,742 B]
Get:20 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 64x64@2 Icons [29 B]
Get:21 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 c-n-f Metadata [1,344 B]
Fetched 993 kB in 1s (673 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt li...

[Launchpad Janitor (janitor)]

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

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

  * d/systemd.prerm: call d-s-h update-state for resolved on upgrades
    (LP: #2078555)

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

  [ Ioanna Alifieraki ]
  * network: skip to reassign master ifindex if already set
    (LP: #2003250)

  [ Nick Rosbrook ]
  * network: do not bring down a bonding port interface when it is already joined
    (This is a follow-up commit required for LP: 2003250)

  * networkd-test: skip test_resolved_domain_restricted_dns
    (LP: #2009859)

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

  [ Lukas Märdian ]
  * Fixing GRE6 and VTI6 on newer kernels (LP: #2037667)

  [ Nick Rosbrook ]
  * debian/tests/tests-in-lxd: update workaround patch (LP: #2055200)

  [ Chengen Du ]
  * udev: Handle PTP device symlink properly on udev action 'change'
    (LP: #2077779)

 -- Nick Rosbrook <email address hidden> Thu, 20 Feb 2025 08:24:02 -0500