RHSA-2024:10948 - Security Advisory

Topic

A new version of Red Hat OpenShift distributed tracing platform (Tempo) has been released

Description

Red Hat OpenShift distributed tracing platform based on Tempo. Tempo is an open-source, easy-to-use, and highly scalable distributed tracing backend. It provides observability for microservices architectures by allowing developers to track requests as they flow through distributed systems. Tempo is optimized to handle large volumes of trace data and is designed to be highly performant even under heavy loads.

• https://docs.redhat.com/en/documentation/openshift_container_platform/4.17 /html/distributed_tracing/distributed-tracing-platform-tempo

Solution

For details on how to apply this update, refer to:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/h tml/operators/administrator-tasks#olm-upgrading-operators

Affected Products

• Red Hat OpenShift distributed tracing

Fixes

• https://issues.redhat.com/browse/TRACING-4933 - Hitting F5 in the monitor tab of Jaeger UI results in a 404 when using the gateway
• https://issues.redhat.com/browse/TRACING-4932 - Enabling .spec.observability.tracing results in a crashloop of tempo-gateway-opa
• https://issues.redhat.com/browse/TRACING-4840 - OpenShift Console doesn't show the "" value for the spec.template.queryFrontend.jaegerQuery.ingress.type
• https://issues.redhat.com/browse/TRACING-4757 - Cannot scrape Tempo query frontend metrics endpoint if non-multitenant TempoStack is created.
• https://issues.redhat.com/browse/TRACING-4568 - Tempo and OpenTelemetry documentation for must-gather
• https://issues.redhat.com/browse/TRACING-4566 - Must gather for OpenTelemetry and Tempo Operators
• https://issues.redhat.com/browse/TRACING-4559 - Documentation improvement to include details for replicationFactor
• https://issues.redhat.com/browse/TRACING-4511 - Tempo: Jaeger UI queries fail with a 504 Gateway Time-out depending on result size and number of traces sent to TempoStack.
• https://issues.redhat.com/browse/TRACING-4507 - Failed to create memberlist ("no private IP address found") on TempoStack
• https://issues.redhat.com/browse/TRACING-4183 - FIPS compliance in Tempo
• https://issues.redhat.com/browse/TRACING-3545 - RHOSDT 2.9 Tempo 2.1.1 does not work on IBM Z (s390x) architecture

CVEs

• CVE-2024-8260

References

• https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/distributed_tracing/distributed-tracing-platform-tempo