Hello Gauthier, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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. ** Description changed: - [SRU TEMPLATE] + [impact] - please see template in bug 1917458 for sru template + the /dev/ptp0 device for a hyperv instance may not be the correct, + hyperv-provided, ptp device. + + [test case] + + on some hyperv instance types, particularly those that might contain + passthrough network card(s) that also provide ptp, the first ptp device + may not be the correct one to use for ptp, e.g. there may be multiple + ones: + + $ ls /dev/ptp* + /dev/ptp0 /dev/ptp1 + $ cat /sys/class/ptp/ptp0/clock_name + hyperv + $ cat /sys/class/ptp/ptp1/clock_name + mlx5_p2p + + the order can change across boots, so a consistent way of addressing the + hyperv-provided one is needed + + [regression potential] + + any regression would involve failure to properly create the ptp symlink, + or other failure while udev is processing newly detected ptp device(s) + + [scope] + + this is needed in all releases + + this was fixed upstream with the commit + 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in + any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913763 Title: hyperv: unable to distinguish PTP devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
