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

Jaeger Collector grpc service port name is wrong in Openshift Service Mesh 2.0.2

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • rhosdt-2.7
    • None
    • Jaeger
    • None
    • True
    • None
    • False

    Description

      grpc traffic to jaeger collector service (deployed by Service Mesh) is not working when the name of the svc is grpc-https. It works when we edit to https-grpc instead.

      Now, this change has been applied manually on the service, but since it's controlled by smcp or jaeger operator, this change might be overwritten.

      One link that describes the issue
      https://github.com/jaegertracing/jaeger-operator/issues/1360

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. OBSDA-217 gRPC traffic to collector service is not working due to wrong port name

          • Undefined - Priority not specified.
          • Closed

          Ticket - Generic Service issue or operations request from an end user TRACING-2878 Regression for TRACING-1300

          • 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

              bbongart@redhat.com Benedikt Bongartz
              rhn-support-atn Anand T N (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: