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

curling for clock class terminates with exit code 7 after side car is restarted

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.14.z, 4.18.z
    • Networking / ptp
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • None
    • None
    • CNF RAN Sprint 275
    • 1
    • In Progress
    • Bug Fix
    • Hide
      Before this release, there was a period when the event data was not yet available when the `cloud-event-proxy` container or pod rebooted. This caused the `getCurrenState` function to incorrectly return a `clockclass` of 0. With this release, the `getCurrentState` function no longer returns an incorrect ‘clockclass` and instead returns an HTTP `400 Bad Request` or `404 Not Found Error`. (link:https://issues.redhat.com/browse/OCPBUGS-60267[OCPBUGS-60267])
      Show
      Before this release, there was a period when the event data was not yet available when the `cloud-event-proxy` container or pod rebooted. This caused the `getCurrenState` function to incorrectly return a `clockclass` of 0. With this release, the `getCurrentState` function no longer returns an incorrect ‘clockclass` and instead returns an HTTP `400 Bad Request` or `404 Not Found Error`. (link: https://issues.redhat.com/browse/OCPBUGS-60267 [ OCPBUGS-60267 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-59984. The following is the description of the original issue:

      Description of problem:

      When killing side car of openshift-ptp pod, curling for clock class terminates with exit code 7 after side car is restarted 

      Version-Release number of selected component (if applicable):

      - OCP 4.14.25
      - ptp-operator.v4.14.0-202506112307

      Steps to Reproduce:

      1.Run ptp and verify clock class with event enabled 
      
      2.verify localhost9091:metrics  for clock class , should be 6  
      
      $ oc exec -it ds/linuxptp-daemon  -n openshift-ptp -c linuxptp-daemon-container -- curl -s localhost:9091/metrics | grep clock_class
      
      3.kill side car (daemon should be still running ) 
        
      $ oc exec ds/linuxptp-daemon -c cloud-event-proxy -n openshift-ptp -- sh -c "kill -9 \$(ps aux | grep cloud-event-proxy | grep -v grep | awk '{print \$2}')"
      
       4. wait for the side car to recover 
      
       5. verify the clock class metrics again
      
          
      

      Actual results:

      $ oc exec -it ds/linuxptp-daemon  -n openshift-ptp -c linuxptp-daemon-container -- curl -s localhost:9091/metrics | grep clock_class
      command terminated with exit code 7

      Expected results:

       should report back metrics

      Additional info:

      In case linuxptp-daemon pod is deleted everything works again
      
      This is a follow up to https://issues.redhat.com/browse/OCPBUGS-56127
      
      
      
      
      

              jacding@redhat.com Jack Ding
              rhn-support-dmoessner Daniel Moessner
              None
              None
              Bonnie Block Bonnie Block
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: