Also requires change in https://github.com/openshift/linuxptp-daemon/pull/67
The issue is validate via version 4.9.18 ptp-operator.4.9.0-202201261125 PTP Operator 4.9.0-202201261125 Succeeded [obochan@obochan ~]$ oc version Client Version: 4.8.0 Server Version: 4.9.18 Kubernetes Version: v1.22.3+e790d7f [obochan@obochan ~]$ did multiple value changes and it works. ps -ef | grep ptp4l root 250306 48228 0 21:07 ? 00:00:00 /usr/sbin/phc2sys -a -r -n 24 -m -u 1 -z /var/run/ptp4l.0.socket -t [ptp4l.0.config] root 250370 48228 0 21:07 ? 00:00:02 /usr/sbin/ptp4l -f /var/run/ptp4l.0.config -2 -s --summary_interval -4 -m root 296546 292935 0 21:24 pts/0 00:00:00 grep --color=auto ptp4l [root@cnfocto2 /]# ch chacl chage chardetect chcon chcpu chgpasswd chgrp chkconfig chmem chmod chown chpasswd chroot chrt [root@cnfocto2 /]# chrt 250370 chrt: bad usage Try 'chrt --help' for more information. [root@cnfocto2 /]# chrt -p 250370 pid 250370's current scheduling policy: SCHED_FIFO pid 250370's current scheduling priority: 65
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 (OpenShift Container Platform 4.9.19 bug fix 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:0340