Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2057072

Summary: Summary Interval Hardcoded in PTP Operator if Set in the Global Body Instead of Command Line
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Joseph Richard <josricha>
Networking sub component: ptp QA Contact: obochan <obochan>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: anusaxen, aputtur, cback, josricha, keyoung
Version: 4.9   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-08 09:56:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2055358    
Bug Blocks:    

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