Closed vaikas closed 3 years ago
@xtreme-sameer-vohra would you mind taking a look since you were playing with traces for IMC?
Assuming this failed due to the same reason as #4745 And is now happy in the latest run
@vaikas going to close this but feel free to re-open if I didn't address the problem.
/close
@xtreme-sameer-vohra: Closing this issue.
/assign
Span references a parentID 8ac255f4ed4407e6
that isn't present in the list of spans captured in the latest failure
{
"timestamp": 1610686222424325,
"duration": 2045499,
"traceId": "0aaf0da82a519fe156732f59b460a352",
"id": "4f4471391eb85d35",
"parentId": "8ac255f4ed4407e6",
"name": "/test-broker-tracing-in-memory-channel-messaging-knative-demk484/br",
"kind": "SERVER",
"localEndpoint": {
"serviceName": "broker-ingress.mink-system",
"ipv4": "10.96.61.2"
},
"annotations": [
{
"timestamp": 1610686222425551,
"value": "Received 35 bytes"
}
],
"tags": {
"http.host": "broker-ingress.mink-system.svc.c487043867.local",
"http.method": "POST",
"http.path": "/test-broker-tracing-in-memory-channel-messaging-knative-demk484/br",
"http.status_code": "202",
"http.url": "/test-broker-tracing-in-memory-channel-messaging-knative-demk484/br",
"http.user_agent": "Go-http-client/1.1",
"opencensus.status_description": "OK"
}
},
which then caused a failure here
The span above with timestamp 1610686222424325
was the oldest span captured, its parent wasn't.
It looks like the same issue in the previous failure where span with ID 06220831e15ea802
is missing
{
"timestamp": 1610628967508395,
"duration": 77040,
"traceId": "7dc09e59099b1a78e430e9364e8877f0",
"id": "e62b47f608b98c7b",
"parentId": "06220831e15ea802",
"name": "/test-broker-tracing-in-memory-channel-messaging-knative-dec26fp/br",
"kind": "SERVER",
"localEndpoint": {
"serviceName": "broker-ingress.mink-system",
"ipv4": "10.96.95.252"
},
"annotations": [
{
"timestamp": 1610628967508418,
"value": "Received 35 bytes"
}
],
"tags": {
"http.host": "broker-ingress.mink-system.svc.c485363944.local",
"http.method": "POST",
"http.path": "/test-broker-tracing-in-memory-channel-messaging-knative-dec26fp/br",
"http.status_code": "202",
"http.url": "/test-broker-tracing-in-memory-channel-messaging-knative-dec26fp/br",
"http.user_agent": "Go-http-client/1.1",
"opencensus.status_description": "OK"
}
},
The span above with timestamp 1610628967508395
was the oldest span captured, its parent wasn't.
@xtreme-sameer-vohra looking at the related updates, is this something that might be solved/able to close?
Hey @lberk,
Unfortunately this was a flake and we don't have a reproducible failure case. It is possible bumping zipkin https://github.com/knative/eventing/pull/4755 solved the issue 🤷
I took a look through MinKinD Upstream E2Es tests and don't see the issue in the last ~5 days.
@vaikas please feel free to re-open this if you notice the explicit failure no root spans found in the trace
/close
@xtreme-sameer-vohra: Closing this issue.
Describe the bug
TestBrokerTracing failed to get a trace here: https://github.com/mattmoor/mink/runs/1701843155?check_suite_focus=true#step:11:42
Expected behavior Tests to pass
To Reproduce First time I've seen this fail.
Knative release version HEAD
Additional context Add any other context about the problem here such as proposed priority