-
Ticket
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
The jaeger-agent injected in pods that are part of Service-Mesh (also have the istio-proxy container injected) return the error:
Err :connection error: desc = \"transport: authentication handshake failed: tls: first record does not look like a TLS handshake\". Reconnecting...","system":"grpc","grpc_log":true}
As per https://issues.redhat.com/browse/TRACING-1300 this was fixed in Jaeger 1.17, but the issue is present in Jaeger v1.30 and v1.38.
# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.6 True False 38h Cluster version is 4.11.6 # oc get csv NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.5.5.3 OpenShift Elasticsearch Operator 5.5.3 Succeeded jaeger-operator.v1.38.0-2 Red Hat OpenShift distributed tracing platform 1.38.0-2 jaeger-operator.v1.36.0-2 Succeeded kiali-operator.v1.48.3 Kiali Operator 1.48.3 kiali-operator.v1.48.2 Succeeded servicemeshoperator.v2.2.3 Red Hat OpenShift Service Mesh 2.2.3-0 servicemeshoperator.v2.2.2 Succeeded
- relates to
-
TRACING-2967 Jaeger Collector grpc service port name is wrong in Openshift Service Mesh 2.0.2
-
- Closed
-
-
-
- Closed
-
- links to