Description of problem: Our example DU policy runs the PTP daemon on workers and masters. This is fine for SNO and 3-node clusters, where all workers are also masters, but not correct for standard clusters, where only workers should be running PTP. How reproducible: 100% Steps to Reproduce: 1. Deploy a standard cluster and DU profile with ZTP 2. Check where the ptp daemon pods are running Actual results: The PTP daemon is running on all nodes Expected results: The PTP daemon is only running on worker nodes Additional info: This can be accomplished by adding the following to the PtpOperatorConfig spec: > daemonNodeSelector: > node-role.kubernetes.io/worker: ""
Verified fixed on a standard 5-node cluster: [josclark@registry ~]$ oc get nodes NAME STATUS ROLES AGE VERSION helix16.lab.eng.tlv2.redhat.com Ready worker 8h v1.23.3+2e8bad7 helix17.lab.eng.tlv2.redhat.com Ready master 8h v1.23.3+2e8bad7 helix23.lab.eng.tlv2.redhat.com Ready worker 8h v1.23.3+2e8bad7 helix26.lab.eng.tlv2.redhat.com Ready master 8h v1.23.3+2e8bad7 helix27.lab.eng.tlv2.redhat.com Ready master 8h v1.23.3+2e8bad7 In this example, helix16 and helix23 are the worker nodes. [josclark@registry ~]$ oc get pods -A|grep -i linuxptp-daemon |awk {'print $2'} |while read POD; do oc get pod -n openshift-ptp $POD -o yaml |grep nodeName: ; done nodeName: helix16.lab.eng.tlv2.redhat.com nodeName: helix23.lab.eng.tlv2.redhat.com PTP pods are only running on the worker nodes.
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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056