Description of problem: https://issues.redhat.com/browse/TRACING-2610 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Use in combination with Jaegertracing 1.34 2. 3. Actual results: Expected results: Additional info: https://github.com/openshift/origin-aggregated-logging/pull/2255
Verified on elasticsearch-operator.4.6.0-202208241715. oc get pods NAME READY STATUS RESTARTS AGE elasticsearch-cdm-openshiftoperatorsesrollover-1-7f6f7d5c58r5jh 2/2 Running 0 6m54s es-rollover-collector-6c6c96765b-zn9rq 1/1 Running 0 5m52s es-rollover-es-index-cleaner-1662004440-w62ls 0/1 Completed 0 5m30s es-rollover-es-index-cleaner-1662004560-slsq7 0/1 Completed 0 3m29s es-rollover-es-index-cleaner-1662004680-qpjjk 0/1 Completed 0 88s es-rollover-es-rollover-create-mapping-8nkkg 0/1 Completed 0 6m es-rollover-query-56c999db5f-nbqkc 2/2 Running 0 5m52s jaeger-operator-7ccbfd465c-mp6cn 2/2 Running 0 9m20s
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 (Moderate: OpenShift Container Platform 4.6.61 security and extras 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:6263