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.
** Changed in: systemd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Incomplete
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => Incomplete
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2077779
Title:
PTP device symlink missing after running udevadm trigger command
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Incomplete
Status in systemd source package in Jammy:
Incomplete
Status in systemd source package in Noble:
Incomplete
Status in systemd source package in Oracular:
Fix Released
Bug description:
[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 <chengen...@canonical.com>
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 <chengen...@canonical.com>
[Test Plan]
1. Create a VM on Azure.
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`.
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2077779/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
