-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhosdt-3.8.2
-
None
jaeger-grpc port seems to be closed in Tempo 0.20, but the service is available in port 16685 as well:
name: jaeger-query ports: - containerPort: 16685 - name: jaeger-grpc protocol: TCP - containerPort: 16686 - name: jaeger-ui protocol: TCP - containerPort: 16687 - name: jaeger-metrics protocol: TCP
From a pod in the same namespace:
/ # nc -zv tempo-sample-query-frontend.tracing-system 16686 tempo-sample-query-frontend.tracing-system (172.30.14.34:16686) open / # nc -zv tempo-sample-query-frontend.tracing-system 16685 nc: tempo-sample-query-frontend.tracing-system (172.30.14.34:16685): Operation timed out
In version 0.19:
/ # nc -zv tempo-sample-query-frontend.tracing-system 16686 tempo-sample-query-frontend.tracing-system (172.30.82.188:16686) open / # nc -zv tempo-sample-query-frontend.tracing-system 16685 tempo-sample-query-frontend.tracing-system (172.30.82.188:16685) open
We detected as our testing pipeline is using the grpc port, logs from Kiali:
Could not fetch traces.
GetAppTraces, Jaeger GRPC client error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 172.30.14.34:16685: i/o timeout"
We also set the example config in the docs using grpc, so the change could impact some customers (Ref. https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/service_mesh/service-mesh-2-x#ossm-configuring-distr-tracing-tempo_observability)
- relates to
-
-
- In Progress
-