Bug 1991834

Summary:	[RFE] Add udev rule to create /dev/ptp_hyperv symlink
Product:	Red Hat Enterprise Linux 8	Reporter:	Husam Ahmed Chaudhary <huchaudh>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	dtardon, ffotorel, peter.vreman, rmetrich, systemd-maint-list, yuxisun
Target Milestone:	beta	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-239-53.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 15:25:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Husam Ahmed Chaudhary 2021-08-10 07:05:14 UTC

Description of problem:

If multiple PTP devices are present then it becomes difficult to configure chronyd with the correct clock source. Because PTP device corresponding to the hyperv host might be /dev/ptp0 or it might be /dev/ptp1.

To solve this problem, add a udev rule that creates the symlink /dev/ptp_hyperv to whichever /dev/ptp entry corresponds to the hyperv host. 

This has already been implemented upstream with the following patch.

https://github.com/systemd/systemd/commit/32e868f058da8b90add00b2958c516241c532b70

Requesting to backport this patch in systemd shipped with RHEL.

Comment 3 Plumber Bot 2021-11-19 15:11:15 UTC

fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/224

Comment 11 errata-xmlrpc 2022-05-10 15:25:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2069