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

Tracing not enabled in kiali when using production-elasticsearch template in SMCP

XMLWordPrintable

    • OSSM 2.2 - 4, Sprint 50, Sprint 51, Sprint 52, Sprint 53

      When setting spec.istio.tracing.jaeger.template in SMCP to production-elasticsearch the jaeger is not enabled in kiali CR.

       

      Steps to reproduce:

      1. install the latest versions of operators from redhat-operators (elasticsearch-operator.4.4.0-202006160135, jaeger-operator.v1.17.3, kiali-operator.v1.12.13, servicemeshoperator.v1.1.3)
      2. Create istio-system project
      3. Create attached SMCP in istio-system project

      Tracing is disabled in created kiali CR (see attached kiali-kiali.yaml)

      Tracing is enabled when using all-in-one template instead of production-elasticsearch.

      Tested on OCP 4.5.RC.2 and OCP 4.4.

      Istio and kiali operators logs are attached.
       
       

        1. istio-operator-54684db956-xgdwv-istio-operator.log
          305 kB
        2. jaeger-operator-85bcf84446-dxbx9-jaeger-operator.log
          2 kB
        3. jk-jaeger-cr.yaml
          6 kB
        4. jk-kiali-cr.yaml
          6 kB
        5. jk-smcp-cr.yaml
          11 kB
        6. Kiali_UI_Jaeger_link_Issue.txt
          6 kB
        7. kiali-kiali.yaml
          9 kB
        8. kiali-operator-757f87cd-wcs6g-ansible.log
          317 kB
        9. kiali-operator-757f87cd-wcs6g-operator.log
          102 kB
        10. smcp.yml
          0.8 kB
        11. SMCP-V2.2.yaml
          0.5 kB

              jewertow@redhat.com Jacek Ewertowski
              fbrychta@redhat.com Filip Brychta
              Votes:
              1 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: