Bug 2060492
| Summary: | Update PtpConfigSlave source-crs to use network_transport L2 instead of UDPv4 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Marius Cornea <mcornea> | ||||
| Component: | Networking | Assignee: | Joseph Richard <josricha> | ||||
| Networking sub component: | ptp | QA Contact: | obochan <obochan> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | high | ||||||
| Priority: | unspecified | CC: | achernet, imiller, keyoung, trozet, vgrinber | ||||
| Version: | 4.10 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.11.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||
| Doc Text: |
network_transport should be L2 and not UDPv4 in all documented ptp configs (e.g. https://docs.openshift.com/container-platform/4.9/networking/using-ptp.html#configuring-linuxptp-services-as-boundary-clock_using-ptp). Note that this applies in all versions as we do not support UDPv4 ptp.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-08-10 10:52:11 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: | |||||||
| Attachments: |
|
||||||
|
Description
Marius Cornea
2022-03-03 15:42:46 UTC
Marius, Have you set the mitigation required for https://bugzilla.redhat.com/show_bug.cgi?id=1992173 provisioned? See https://bugzilla.redhat.com/show_bug.cgi?id=1992173#c19. /KenY (In reply to Ken Young from comment #1) > Marius, > > Have you set the mitigation required for > https://bugzilla.redhat.com/show_bug.cgi?id=1992173 provisioned? See > https://bugzilla.redhat.com/show_bug.cgi?id=1992173#c19. > > /KenY I haven't set the mitigation mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1992173#c19 . I tried changing the priority (chrt -f -p 65 $pid) of the existing ice-ptp and ptp4l processes but the linuxptp-daemon-container log shows the same error. Nevertheless I see the BZ mentions a more recent NIC firmware than what I have on my system so I'll try updating the firmware and re-try. After the firmware update and adjusting the priorities I can no longer see the faults in the ptp logs. Ofer also noticed that the ptp config set on my machine was using `network_transport UDPv4` while it should be `network_transport L2`. This config comes from the ZTP source CRs: https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.10/ztp/source-crs/PtpConfigSlave.yaml#L99 https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.10/ztp/source-crs/PtpConfigSlaveCvl.yaml#L100 @Ken, I updated this BZ to keep track of updating the ptp configs source CRs to use `network_transport L2` instead of `network_transport UDPv4` as I understand L2 is the supported mode currently. It(In reply to Marius Cornea from comment #3) > After the firmware update and adjusting the priorities I can no longer see > the faults in the ptp logs. > > Ofer also noticed that the ptp config set on my machine was using > `network_transport UDPv4` while it should be `network_transport L2`. This > config comes from the ZTP source CRs: > > https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.10/ztp/ > source-crs/PtpConfigSlave.yaml#L99 > https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.10/ztp/ > source-crs/PtpConfigSlaveCvl.yaml#L100 > > @Ken, I updated this BZ to keep track of updating the ptp configs source CRs > to use `network_transport L2` instead of `network_transport UDPv4` as I > understand L2 is the supported mode currently. While the transport is set to UDP4 in the config file options, it is overridden by the command line options. The command line options for ptp4l are selecting IEEE 802.3 transport: https://github.com/openshift-kni/cnf-features-deploy/blob/d521e22a7c1a8dcd0a76f2c4659da8736defec49/ztp/source-crs/PtpConfigSlave.yaml#L13 ptp4lOpts: "-2 -s --summary_interval -4" The "-2" is for selecting the IEEE 802.3 transport, according to https://linux.die.net/man/8/ptp4l It's therefore possible that the observed behavior is not related to the ptp4l configuration. Having said that, it's probably a good idea to remove duplicate and seemingly conflicting settings from ptp4lOpts and ptp4lConf to reduce confusion, but this is not a functional / performance issue. Issue is validated via the PR changed the configuration from UDP to L2. 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069 |