Bug 2040799

Have another incident of this in a 4.9 deployment. summary_interval is set to 6 and logSyncInterval is set to -4. Receiving the same error re: the webhook.

What problem/issue/behavior are you having trouble with?  What do you expect to see?
When using "summary_interval 6" in a PtpConfig the ptpconfigvalidationwebhook returns an error
=======================================================================
Error from server (summary_interval 6 must match logSyncInterval -4): error when creating "04-PtpConfigBC.yaml": admission webhook "ptpconfigvalidationwebhook.openshift.io" denied the request: summary_interval 6 must match logSyncInterval -4
=======================================================================
This is a perfectly valid configuration though. summary_interval does not at all have to match logSyncInterval according to the ptp4l manual page.

The PtpConfig file is the following:
=======================================================================
apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: boundary
  namespace: openshift-ptp
spec:
  profile:
  - name: "boundary"
    interface: ""
    ptp4lOpts: "-2 --summary_interval 6"

    phc2sysOpts: "-a -r -n 24"
    ptp4lConf: |
      [ens1f0]
      masterOnly 0
      [ens1f1]
      masterOnly 1
      [ens1f2]
      masterOnly 1
      [global]
      slaveOnly               0
      priority1 128
      domainNumber 24
      boundary_clock_jbod 1
      logAnnounceInterval -3
      delay_mechanism E2E
      network_transport L2
      tx_timestamp_timeout 50
      dataset_comparison G.8275.x
      time_stamping hardware
      clockClass 255
      logSyncInterval -4
      logMinDelayReqInterval -4
      fault_reset_interval 0
      priority2 128
      clock_servo linreg
  recommend:
  - profile: "boundary"
    priority: 4
    match:
    - nodeLabel: "node-role.kubernetes.io/master"

What operator build are you still seeing this in?

Openshift version is 4.9, Operator details below;

ptp-operator.4.9.0.202202070644

Let me know if you need any other details.

issue is verfied in v4.10 all the details below.

[kni@ran-vcl01-installer ~]$ oc version 
Client Version: 4.9.0-0.nightly-2022-02-28-053011
Server Version: 4.10.4
Kubernetes Version: v1.23.3+e419edf
[kni@ran-vcl01-installer ~]$ oc get csv -A | grep -i ptp
openshift-ptp                                      performance-addon-operator.v4.10.1           Performance Addon Operator                               4.10.1                           Succeeded
openshift-ptp                                      ptp-operator.4.10.0-202203081809             PTP Operator                                             4.10.0-202203081809              Succeeded
[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp
NAME           AGE
du-ptp-slave   6d

[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp -o yaml | grep -i summary\|logsync

[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp -o yaml | grep -i 'summary\|logsync'
        {"apiVersion":"ptp.openshift.io/v1","kind":"PtpConfig","metadata":{"annotations":{},"creationTimestamp":"2022-02-09T08:42:42Z","generation":6,"name":"du-ptp-slave","namespace":"openshift-ptp","resourceVersion":"4268397","uid":"b9945c2f-e50a-4cfd-a6a6-3f1f46d86826"},"spec":{"profile":[{"interface":"ens7f1","name":"slave","phc2sysOpts":"-a -r -n 24 -u 1 -m","ptp4lConf":"[global]\n#\n# Default Data Set\n#\ntwoStepFlag 1\nslaveOnly 1\npriority1 128\npriority2 128\ndomainNumber 24\n#utc_offset 37\nclockClass 248\nclockAccuracy 0xFE\noffsetScaledLogVariance 0xFFFF\nfree_running 0\nfreq_est_interval 1\ndscp_event 0\ndscp_general 0\ndataset_comparison ieee1588\nG.8275.defaultDS.localPriority 128\n#\n# Port Data Set\n#\nlogAnnounceInterval -3\nlogSyncInterval 2\nlogMinDelayReqInterval -4\nlogMinPdelayReqInterval -4\nannounceReceiptTimeout 3\nsyncReceiptTimeout 0\ndelayAsymmetry 0\nfault_reset_interval 4\nneighborPropDelayThresh 20000000\nmasterOnly 0\nG.8275.portDS.localPriority 128\n#\n# Run time options\n#\nassume_two_step 0\nlogging_level 6\npath_trace_enabled 0\nfollow_up_info 0\nhybrid_e2e 0\ninhibit_multicast_service 0\nnet_sync_monitor 0\ntc_spanning_tree 0\ntx_timestamp_timeout 1\nunicast_listen 0\nunicast_master_table 0\nunicast_req_duration 3600\nuse_syslog 1\nverbose 0\nkernel_leap 1\ncheck_fup_sync 0\n#\n# Servo Options\n#\npi_proportional_const 0.0\npi_integral_const 0.0\npi_proportional_scale 0.0\npi_proportional_exponent -0.3\npi_proportional_norm_max 0.7\npi_integral_scale 0.0\npi_integral_exponent 0.4\npi_integral_norm_max 0.3\nstep_threshold 0.0\nfirst_step_threshold 0.00002\nmax_frequency 900000000\nclock_servo pi\nsanity_freq_limit 200000000\nntpshm_segment 0\n#\n# Transport options\n#\ntransportSpecific 0x0\nptp_dst_mac 01:1B:19:00:00:00\np2p_dst_mac 01:80:C2:00:00:0E\nudp_ttl 1\nudp6_scope 0x0E\nuds_address /var/run/ptp4l\n#\n# Default interface options\n#\nclock_type OC\nnetwork_transport UDPv4\ndelay_mechanism E2E\ntime_stamping hardware\ntsproc_mode filter\ndelay_filter moving_median\ndelay_filter_length 10\negressLatency 0\ningressLatency 0\nboundary_clock_jbod 0\n#\n# Clock description\n#\nproductDescription ;;\nrevisionData ;;\nmanufacturerIdentity 00:00:00\nuserDescription ;\ntimeSource 0xA0\n","ptp4lOpts":"-2 --summary_interval 4 -m","ptpSchedulingPolicy":"SCHED_FIFO","ptpSchedulingPriority":65}],"recommend":[{"match":[{"nodeLabel":"node-role.kubernetes.io/master"}],"priority":4,"profile":"slave"}]}}
        logSyncInterval 2
      ptp4lOpts: -2 --summary_interval 4 -m

issue is verfied in v4.10 all the details below.

[kni@ran-vcl01-installer ~]$ oc version 
Client Version: 4.9.0-0.nightly-2022-02-28-053011
Server Version: 4.10.4
Kubernetes Version: v1.23.3+e419edf
[kni@ran-vcl01-installer ~]$ oc get csv -A | grep -i ptp
openshift-ptp                                      performance-addon-operator.v4.10.1           Performance Addon Operator                               4.10.1                           Succeeded
openshift-ptp                                      ptp-operator.4.10.0-202203081809             PTP Operator                                             4.10.0-202203081809              Succeeded
[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp
NAME           AGE
du-ptp-slave   6d

[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp -o yaml | grep -i summary\|logsync

[kni@ran-vcl01-installer ~]$ oc get ptpconfigs.ptp.openshift.io -n openshift-ptp -o yaml | grep -i 'summary\|logsync'
        {"apiVersion":"ptp.openshift.io/v1","kind":"PtpConfig","metadata":{"annotations":{},"creationTimestamp":"2022-02-09T08:42:42Z","generation":6,"name":"du-ptp-slave","namespace":"openshift-ptp","resourceVersion":"4268397","uid":"b9945c2f-e50a-4cfd-a6a6-3f1f46d86826"},"spec":{"profile":[{"interface":"ens7f1","name":"slave","phc2sysOpts":"-a -r -n 24 -u 1 -m","ptp4lConf":"[global]\n#\n# Default Data Set\n#\ntwoStepFlag 1\nslaveOnly 1\npriority1 128\npriority2 128\ndomainNumber 24\n#utc_offset 37\nclockClass 248\nclockAccuracy 0xFE\noffsetScaledLogVariance 0xFFFF\nfree_running 0\nfreq_est_interval 1\ndscp_event 0\ndscp_general 0\ndataset_comparison ieee1588\nG.8275.defaultDS.localPriority 128\n#\n# Port Data Set\n#\nlogAnnounceInterval -3\nlogSyncInterval 2\nlogMinDelayReqInterval -4\nlogMinPdelayReqInterval -4\nannounceReceiptTimeout 3\nsyncReceiptTimeout 0\ndelayAsymmetry 0\nfault_reset_interval 4\nneighborPropDelayThresh 20000000\nmasterOnly 0\nG.8275.portDS.localPriority 128\n#\n# Run time options\n#\nassume_two_step 0\nlogging_level 6\npath_trace_enabled 0\nfollow_up_info 0\nhybrid_e2e 0\ninhibit_multicast_service 0\nnet_sync_monitor 0\ntc_spanning_tree 0\ntx_timestamp_timeout 1\nunicast_listen 0\nunicast_master_table 0\nunicast_req_duration 3600\nuse_syslog 1\nverbose 0\nkernel_leap 1\ncheck_fup_sync 0\n#\n# Servo Options\n#\npi_proportional_const 0.0\npi_integral_const 0.0\npi_proportional_scale 0.0\npi_proportional_exponent -0.3\npi_proportional_norm_max 0.7\npi_integral_scale 0.0\npi_integral_exponent 0.4\npi_integral_norm_max 0.3\nstep_threshold 0.0\nfirst_step_threshold 0.00002\nmax_frequency 900000000\nclock_servo pi\nsanity_freq_limit 200000000\nntpshm_segment 0\n#\n# Transport options\n#\ntransportSpecific 0x0\nptp_dst_mac 01:1B:19:00:00:00\np2p_dst_mac 01:80:C2:00:00:0E\nudp_ttl 1\nudp6_scope 0x0E\nuds_address /var/run/ptp4l\n#\n# Default interface options\n#\nclock_type OC\nnetwork_transport UDPv4\ndelay_mechanism E2E\ntime_stamping hardware\ntsproc_mode filter\ndelay_filter moving_median\ndelay_filter_length 10\negressLatency 0\ningressLatency 0\nboundary_clock_jbod 0\n#\n# Clock description\n#\nproductDescription ;;\nrevisionData ;;\nmanufacturerIdentity 00:00:00\nuserDescription ;\ntimeSource 0xA0\n","ptp4lOpts":"-2 --summary_interval 4 -m","ptpSchedulingPolicy":"SCHED_FIFO","ptpSchedulingPriority":65}],"recommend":[{"match":[{"nodeLabel":"node-role.kubernetes.io/master"}],"priority":4,"profile":"slave"}]}}
        logSyncInterval 2
      ptp4lOpts: -2 --summary_interval 4 -m

Hi team,

Is there any further info you need from us?  If not to we have an ETA on this BZ?  Thank you in advance

Thanks,
Alan

Hi Team,

Just following up on this.

Thanks,
Alan

Hi All,

We haven't heard back/an update from this report in awhile. Any new news we can pass along to the customer?

Thanks in advance,

Darren Carpenter