Are you in #kiali channel in freenode?
Yes, I’m in the freenode chat. I have the name of gummy.
Thanks again for your time sherwoodzern. Int he call we saw that the embedded feature in jaeger is not working in your environment.
Istio 1.1.4 has the version 1.9 of docker.io/jaegertracing (You can check this in https://github.com/istio/istio/blob/bc7465793cbff4c4189639b3f404e21c517cbdc6/install/kubernetes/helm/istio/charts/tracing/values.yaml)
I have the version 1.9.0-3 and it’s works so maybe the jaeger version is wrong.
So can you launch this command and show me the output? This command return the Image version of jaeger.
kubectl describe podkubectl get pods | grep jaeger-query | awk ‘{ print $1 }’| grep "Image:" | awk '{ print $2}'
Alberto,
Are you sure that is the command you want me to use? That won't
work.
I captured the following:
kubectl describe po istio-tracing-7454db9d79-56xr4 -n
istio-system
Containers:
jaeger:
Container ID:
docker://e0db0393536a6c8988b16907535d6cfb799a0c0338603c6467664079750cac40
Image: docker.io/jaegertracing/all-in-one:1.9
Image ID:
docker-pullable://docker.io/jaegertracing/all-in-one@sha256:29c921747eddfa96c97cf96aac0180e97bfdfcbea25e230daef09711103d1f61
Ports: 9411/TCP, 16686/TCP, 5775/UDP, 6831/UDP,
6832/UDP
Host Ports: 0/TCP, 0/TCP, 0/UDP, 0/UDP, 0/UDP
State: Running
Ok I’ll try the version jaegertracing/all-in-one:1.9 and It’s working.
This is my Pod definition
Name: jaeger-6bc64b7c6b-tspbf
Namespace: istio-system
Priority: 0
PriorityClassName: <none>
Node: localhost/192.168.86.28
Start Time: Fri, 10 May 2019 09:30:17 +0200
Labels: app=jaeger
jaeger-infra=jaeger-pod
pod-template-hash=2672063726
Annotations: openshift.io/scc=restricted
prometheus.io/port=16686
prometheus.io/scrape=true
Status: Running
IP: 172.17.0.23
Controlled By: ReplicaSet/jaeger-6bc64b7c6b
Containers:
jaeger:
Container ID: docker://484cdde7d59d93bff4243f4a43215dd3eec0d80b0e8c467054e031d5c0ab4c17
Image: jaegertracing/all-in-one:1.9
Image ID: docker-pullable://jaegertracing/all-in-one@sha256:29c921747eddfa96c97cf96aac0180e97bfdfcbea25e230daef09711103d1f61
Ports: 5775/UDP, 6831/UDP, 6832/UDP, 16686/TCP, 9411/TCP, 5778/TCP
Host Ports: 0/UDP, 0/UDP, 0/UDP, 0/TCP, 0/TCP, 0/TCP
Args:
--memory.max-traces=50000
State: Running
Started: Fri, 10 May 2019 09:30:22 +0200
Ready: True
Restart Count: 0
Limits:
cpu: 500m
memory: 2Gi
Requests:
cpu: 100m
memory: 100Mi
Readiness: http-get http://:14269/ delay=5s timeout=1s period=10s #success=1 #failure=3
Environment:
COLLECTOR_ZIPKIN_HTTP_PORT: 9411
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-hmr8m (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
default-token-hmr8m:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-hmr8m
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/memory-pressure:NoSchedule
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 52s default-scheduler Successfully assigned istio-system/jaeger- 6bc64b7c6b-tspbf to localhost
Normal Pulling 51s kubelet, localhost pulling image "jaegertracing/all-in-one:1.9"
Normal Pulled 47s kubelet, localhost Successfully pulled image "jaegertracing/all-in-one:1.9"
Normal Created 47s kubelet, localhost Created container
Normal Started 47s kubelet, localhost Started container
Can you try to launch this yaml file https://raw.githubusercontent.com/jaegertracing/jaeger-openshift/master/all-in-one/jaeger-all-in-one-template.yml and try the test that we did yesterday? (after results of traces in search add a queryparam uiEmbed=v0 and hit Enter in the keyboard)
Anyway you should should open a issue in Jaeger-UI Issues about the embedded component