Jaeger query not picking up from Elasticsearch

[foggy-glasses]

Hello..
I'm trying to setup Jaeger (production strategy) on an EKS cluster which has multiple services in multiple namespaces. I've followed the guide here https://www.jaegertracing.io/docs/next-release/operator/ and hooked it up to an elasticsearch storage that's running on the same VPC but on an EC2 machine. I've configured the jaegery-query basepath as /trace and hooked the setup to an nginx ingress.

The jaeger operator and other components are deployed in the observability namespace and I've configured one of my deployments in another namepace (added the annotation to deploy the jaeger sidecar) to use Jaeger. I can now see the traces being populated in Elasticsearch. However, the same doesn't show up in the jaeger UI. I can't even see the default jaeger-query as part of the traces.

Here's my YAML deployment file for the Jaeger instance.

# Create the Jaeger instance
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger
  namespace: observability
spec:
  strategy: production
  collector:
    maxReplicas: 20
    options:
      log-level: debug
      es:
        use-aliases: true
        server-urls: http://ec2elasticsearch:9200
    secretName: jaeger-secret
  storage:
    type: elasticsearch
    options:
      es:
        create-index-templates: false
        server-urls: http://ec2elasticsearch:9200
        num-replicas: 0
        index-prefix: test
    secretName: jaeger-secret
  query:
    options:
      log-level: debug
      es:
        use-aliases: true
        server-urls: http://ec2elasticsearch:9200
      query:
        base-path: /trace
    secretName: jaeger-secret
  ingress:
    enabled: false
  ui:
    options: 
      log-level: debug
      dependencies:
        menuEnabled: true

The collector and query logs don't show any errors. I've looked at another issue here which deals with something similar. However, it hasn't helped solved this issue. Is there something I'm missing?

[foggy-glasses]

I had incorrectly stated this as a bug. And I'm unable to change the label either. I'll attempt to raise a new one with the proper label.

[foggy-glasses]

I can't find a way to raise an issue as a question as opposed to a bug nor can I find a way to relabel my issue. Hence, I'm reopening this. I'll be glad if this can re-labelled as a question rather than a bug.

[ahmsay]

I have the same problem as well. Any update yet ?

[devopsING2]

I also have the same problem, with Operator version 1.49.0.
I have the traces which arrive on collector but which are not displayed on the UI interface, there is no error in the logs, whether on the operator, collector, or elasticsearch.

And I would like to point out at the same time that the latest version mentioned in the documentation which is 1.50.0 does not even exist, when I try to access the url https://github.com/jaegertracing/jaeger -operator/releases/download/v1.50.0/jaeger-operator.yaml, this was not found.