Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-2878

Regression for TRACING-1300

    XMLWordPrintable

Details

    • Ticket
    • Resolution: Done
    • Major
    • rhosdt-2.7
    • None
    • Jaeger
    • None
    • False
    • None
    • False

    Description

      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

       

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. TRACING-2967 Jaeger Collector grpc service port name is wrong in Openshift Service Mesh 2.0.2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. TRACING-2873 Jaeger Collector service port name does not match convention - tracking

          • Undefined - Priority not specified.
          • Closed
          links to

          Web Link TLS handshake connection failures between jaeger-agent and jaeger-collector when jaeger-agent is injected as a sidecar.

          Activity

            People

              bbongart@redhat.com Benedikt Bongartz
              rhn-support-asolanas Alexis Solanas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: