-
Bug
-
Resolution: Done
-
Major
-
None
-
4.14.z, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
CNF RAN Sprint 275
-
1
-
In Progress
-
Bug Fix
-
-
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
- blocks
-
OCPBUGS-60570 curling for clock class terminates with exit code 7 after side car is restarted
-
- Closed
-
- clones
-
OCPBUGS-59984 curling for clock class terminates with exit code 7 after side car is restarted
-
- Closed
-
- is blocked by
-
OCPBUGS-59984 curling for clock class terminates with exit code 7 after side car is restarted
-
- Closed
-
- is cloned by
-
OCPBUGS-60570 curling for clock class terminates with exit code 7 after side car is restarted
-
- Closed
-
- links to