Bug 2057072 - Summary Interval Hardcoded in PTP Operator if Set in the Global Body Instead of Command Line
Summary: Summary Interval Hardcoded in PTP Operator if Set in the Global Body Instead ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.z
Assignee: Joseph Richard
QA Contact: obochan
URL:
Whiteboard:
Depends On: 2055358
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-22 17:20 UTC by OpenShift BugZilla Robot
Modified: 2022-12-19 04:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-08 09:56:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift linuxptp-daemon pull 75 0 None Merged [release-4.9] Bug 2057072: Don't set --summary_interval 1 if set in ptp4lconf 2022-03-31 14:45:53 UTC
Red Hat Product Errata RHSA-2022:1158 0 None None None 2022-04-08 09:56:45 UTC

Comment 2 obochan 2022-03-08 10:19:24 UTC 
The issue isn't resolved in v4.9 

i have tested in the following version.

[obochan@obochan cnf-gotests]$ oc version 
Client Version: 4.8.0
Server Version: 4.9.23

In the current version 4.9 i am running i don't see any summary interval inside the container the ptp4l.conf and i see 2 logs in a sec.

see the logs below.

version 4.9
 [ens3f0][root@cnfocto2 /]# cat /var/run/ptp4l.0.config | grep sum
 assume_two_step  0
[root@cnfocto2 /]# exit
exit
[obochan@obochan cnf-gotests]$ oc version 
Client Version: 4.8.0
Server Version: 4.9.23

phc2sys[394497.060]: [ptp4l.0.config] CLOCK_REALTIME rms   11 max   11 freq  +6601 +/-   0 delay   515 +/-   0
phc2sys[394498.060]: [ptp4l.0.config] CLOCK_REALTIME rms   27 max   27 freq  +6636 +/-   0 delay   515 +/-   0
ptp4l[394498.286]: [ptp4l.0.config] rms    6 max   16 freq  -2441 +/-  10 delay   408 +/-   1
phc2sys[394499.060]: [ptp4l.0.config] CLOCK_REALTIME rms   10 max   10 freq  +6607 +/-   0 delay   514 +/-   0
phc2sys[394500.060]: [ptp4l.0.config] CLOCK_REALTIME rms   12 max   12 freq  +6602 +/-   0 delay   517 +/-   0
ptp4l[394500.287]: [ptp4l.0.config] rms    8 max   21 freq  -2446 +/-  13 delay   407 +/-   1
phc2sys[394501.060]: [ptp4l.0.config] CLOCK_REALTIME rms   45 max   45 freq  +6655 +/-   0 delay   514 +/-   0
phc2sys[394502.060]: [ptp4l.0.config] CLOCK_REALTIME rms   58 max   58 freq  +6566 +/-   0 delay   516 +/-   0
ptp4l[394502.288]: [ptp4l.0.config] rms   19 max   33 freq  -2454 +/-  35 delay   408 +/-   1
Comment 3 Joseph Richard 2022-03-08 21:35:50 UTC 
That's 1 ptp4l log every 2 seconds, not 2 per second, which suggests a summary interval of 1.
Also, you can't use oc version to check operator version.  Look at your subscription instead.
What's your ptpconfig?  What is the command line for ptp4l?
Comment 7 obochan 2022-04-05 05:58:41 UTC 
Verfied in version 
[obochan@obochan ~]$ oc version
Client Version: 4.8.0
Server Version: 4.9.27
Kubernetes Version: v1.22.5+a36406b

Validate the command gets the priority over the global summary_interval parameter.
validate when no summary_interval configured default is working 1 message per seconds
Comment 10 errata-xmlrpc 2022-04-08 09:56:15 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 (Important: OpenShift Container Platform 4.9.27 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:1158
Note You need to log in before you can comment on or make changes to this bug.