Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-217

gRPC traffic to collector service is not working due to wrong port name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Undefined
    • None
    • None
    • PM Tracing
    • None
    • False
    • None
    • False
    • 0

    Description

      GitHub issue 1360 issue has introduced a regression https://github.com/jaegertracing/jaeger-operator/issues/1360
      by renaming https-grpc to grpc-https service port name which break the grpc communication to the collector.

      Issue has been confirmed on:
      Red Hat Open Jaeger 1.20.3 (OSSM 2.0.2-0)
      Red Hat Distributed Tracing platform 1.36.0-2 (OSSM 2.2.3-0)

      Collector service YAML from RHDT 1.36.0-2:
      service-jaeger-all-in-one-inmemory-collector.yaml

      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

          Activity

            People

              rh-ee-jgomezse Jose Gomez-Selles
              laurent.tourreau Laurent TOURREAU
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: