-
Bug
-
Resolution: Done
-
Minor
-
4.13
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
No
-
08/Jan: typo fixes merged, QE review not required.
-
None
-
None
-
None
-
T&PS 2023 #10, T&PS 2023 #11, T&PS 2023 #12, T&PS 2023 #13, T&PS 2024 #01
-
5
-
None
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
https://docs.openshift.com/container-platform/4.13/networking/using-ptp.html#configuring-ptp-devices
Configuring PTP devices section: The PtpConfig CR object examples include in recommend.match field both nodeLabel and nodeName match:
match:
- nodeLabel: "node-role.kubernetes.io/worker"
nodeName: "<node_name>"
and this leads to confusion because it is contradictory to the field description in Table 1 and Table 2:.
recommend.match : Specify .recommend.match rules with nodeLabel **or** nodeName
I think the PtpConfig CRs should also only target nodeLabel or nodeName because when following the documentation as it is right now, it is not straight forward that all workers will be configured, as well as <node_name> node.
It seems as if only <node_name> from all workers will be configured, instead of the OR operation that is going on in the match field.
From all the PtpConfig CR examples, I would add one that only contains <node_name> and maybe further explain in the example contaning both of them, that all workers plus <node_name> will be targeted.
Note: In fact, when seeking to apply different profiles to different <node_name> but leaving the nodeLabel field under the match, PTP crashed due to simultaneous ptp4l and phc2sys processes running in the same nodes.
Version-Release number of selected component (if applicable):
4.13+
Raised in https://github.com/openshift/openshift-docs/issues/64717
- links to