Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-39094

PtpOperatorConfig and PtpConfig CRs not compared against the correct reference CRs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 4.18
    • 4.17
    • oc / cluster-compare
    • None
    • Important
    • None
    • Telco kube-compare Sprint 259, Telco kube-compare Sprint 260
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      On a SNO with RAN RDS profile with the following refence CR configured:
      
          - fileName: PtpOperatorConfigForEvent.yaml
            policyName: "config-policy"
          - fileName: PtpConfigBoundaryForEvent.yaml
            policyName: "config-policy"
      
      the cluster compare tool reports the differences below as it compares the configs with the PtpOperatorConfig.yaml and PtpConfigBoundary.yaml reference CRs.

       

      Differences found in CR: ptp.openshift.io/v1_PtpOperatorConfig_openshift-ptp_default, Compared To Reference CR: optional/ptp-config/PtpOperatorConfig.yaml
      diff -u -N /tmp/MERGED-2395906557/ptp-openshift-io-v1_ptpoperatorconfig_openshift-ptp_default /tmp/LIVE-4294047119/ptp-openshift-io-v1_ptpoperatorconfig_openshift-ptp_default
      --- /tmp/MERGED-2395906557/ptp-openshift-io-v1_ptpoperatorconfig_openshift-ptp_default	2024-08-24 12:51:55.621044718 +0000
      +++ /tmp/LIVE-4294047119/ptp-openshift-io-v1_ptpoperatorconfig_openshift-ptp_default	2024-08-24 12:51:55.621044718 +0000
      @@ -6,3 +6,7 @@
       spec:
         daemonNodeSelector:
           node-role.kubernetes.io/master: ""
      +  ptpEventConfig:
      +    apiVersion: $event_api_version
      +    enableEventPublisher: true
      +    transportHost: http://ptp-event-publisher-service-NODE_NAME.openshift-ptp.svc.cluster.local:9043 
      Differences found in CR: ptp.openshift.io/v1_PtpConfig_openshift-ptp_boundary, Compared To Reference CR: required/ptp-operator/PtpConfigBoundary.yaml
      diff -u -N /tmp/MERGED-3064109999/ptp-openshift-io-v1_ptpconfig_openshift-ptp_boundary /tmp/LIVE-4157082257/ptp-openshift-io-v1_ptpconfig_openshift-ptp_boundary
      --- /tmp/MERGED-3064109999/ptp-openshift-io-v1_ptpconfig_openshift-ptp_boundary	2024-08-24 12:51:56.293069480 +0000
      +++ /tmp/LIVE-4157082257/ptp-openshift-io-v1_ptpconfig_openshift-ptp_boundary	2024-08-24 12:51:56.294069517 +0000
      @@ -6,16 +6,11 @@
       spec:
         profile:
         - name: boundary
      -    phc2sysOpts: -a -r -n 24
      +    phc2sysOpts: -a -r -m -n 24 -N 8 -R 16
           ptp4lConf: |
      -      # The interface name is hardware-specific
      -      [$iface_slave]
      +      [ens1f1]
             masterOnly 0
      -      [$iface_master_1]
      -      masterOnly 1
      -      [$iface_master_2]
      -      masterOnly 1
      -      [$iface_master_3]
      +      [ens1f2]
             masterOnly 1
             [global]
             #
      @@ -118,7 +113,7 @@
             manufacturerIdentity 00:00:00
             userDescription ;
             timeSource 0xA0
      -    ptp4lOpts: "-2"
      +    ptp4lOpts: -2 --summary_interval -4
           ptpSchedulingPolicy: SCHED_FIFO
           ptpSchedulingPriority: 10
           ptpSettings: 

       

              jramsay1@redhat.com Jim Ramsay
              mcornea@redhat.com Marius Cornea
              Yogesh Ahire Yogesh Ahire
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: