That issue is critical for IBM Z clusters where tempo tests work only with latest version due what durgin 2.6.6 release we faced issue: https://issues.redhat.com/browse/TRACING-5192
However, I faced the same issue with our clusters too both hive and upi (ipv6/disconnected) what is not critical but it is not expected behaviour

I did not found some code issue in jenkinsfile...

• https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/jenkinsfiles/install-jobs/install-service-mesh-3.jenkinsfile?ref_type=heads#L203
• https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/jenkinsfiles/install-jobs/install-service-mesh-3.jenkinsfile?ref_type=heads#L222
• https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/jenkinsfiles/install-jobs/install-service-mesh.jenkinsfile?ref_type=heads#L238
• https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/src/com/redhat/qe/servicemesh/jenkins/ocp/Utils.groovy?ref_type=heads#L61

Freshly tested ossm3 installation from stage example (10.03.2025):
1. Tempo:

2. OTEL:

Catalogs:

• Tempo: https://catalog.redhat.com/software/containers/rhosdt/tempo-rhel8/642c3e0f1f8255d1c086fb20
• Otel: https://catalog.redhat.com/software/containers/rhosdt/opentelemetry-rhel8-operator/613b50f3a052bb39f2c5f320

With default RH catalog from hive:
1. Tempo:

2. OTEL: