Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-1361

Kiali says Jaeger is unreachable, but user can get to it through Kiali side menu

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • OSSM 2.2.0
    • OSSM 2.2.0
    • Maistra
    • None
    • Sprint 50

      When I install Kiali v1.48 in OSSM 2.2, there is an Istio Component Status Warning message saying jaeger is unreachable. However, the left-hand menu has a "Distributed Tracing" link that, when clicked, takes me to the Jaeger UI successfully.

      We should find out why we are issuing this warning. Either some internal configuration of Kiali in OSSM 2.2 is incorrect (in which case we need the OSSM operator to configure Kiali correctly) or that warning message is incorrect (in which case we need to  fix Kiali so it doesn't report jaeger as being unreachable).

      See attached screenshots.

      Clicking that Distrubted Tracing link shows me the Jaeger UI (that link brought me first to a login page and a permissions page in which I had to log into Jaeger and grant it permissions - but it eventually took me to the Jaeger UI as you see in the attached screenshot).

       

        1. config_2.2.png
          45 kB
          Praneeth Bajjuri
        2. config_error.gif
          282 kB
          Praneeth Bajjuri
        3. kiali-7657d65547-p6dwr-kiali.log
          76 kB
          Praneeth Bajjuri
        4. kiali-kiali.yaml
          11 kB
          Praneeth Bajjuri
        5. Screenshot from 2022-04-13 17-53-14.png
          46 kB
          John Mazzitelli
        6. Screenshot from 2022-04-13 17-53-24.png
          62 kB
          John Mazzitelli
        7. Screenshot-Jaeger-NoError.png
          7 kB
          Sunil Kondkar
        8. Screenshot-kiali-CR.png
          15 kB
          Sunil Kondkar

            jmazzitelli John Mazzitelli
            jmazzitelli John Mazzitelli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: