We faced issue with Tempo on cluster running on IBM Z arch
OCP versions tested: 4.15, 4.17(fips), 4.18(fips)
Tempo Operator: 0.13.0-1+0.1730817419.p

Based on doc¹ we adding: Tempo, TempoStack, OpenTelemetryCollector and update config of smcp.

To test²  configuration we:

1. make few requests to productpage.bookinfo
2. verify tracing through the tempo-sample-query-frontend pod with command as 

   curl -sS "localhost:16686/api/traces?limit=5&lookback=10m&service=productpage.bookinfo" 

Unfortunatelly do not receive any traces and also tempo-sample-ingester-0 failing with 
error³  and later stay in CrashLoopBackOff
 
Contact person on IBM side: dshaik@redhat.com 

Related:

1. doc - https://docs.openshift.com/container-platform/4.18/service_mesh/v2x/ossm-observability.html#ossm-configuring-distr-tracing-tempo_observability
2. test - https://github.com/maistra/maistra-test-tool/blob/main/pkg/tests/ossm/tempo_tracing_test.go#L35
3. tempo-sample-ingester-0.log

Also attach:

• tempo-sample-ingester-0.yaml

• smcp.yaml
• otel-collector_deployment.yaml
• otel-collector_pod.logs

If it is not enough and you need reproducer, please, ping me, I will try to prepare it asap