Describe the bug
Running through the Rate Limit task on istio.io, I went to check the tracespan data in Jaeger. I discovered that the istio-mixer spans show up as disconnected from their parent spans, and the traces are labeled as trace-without-root-span.

Meanwhile, the parent traces show the UAEX codes that we would expect, but don't have the Mixer traces.

Expected behavior
Mixer traces to be part of the distributed traces for the parent requests.

Steps to reproduce the bug
Rate limit task w/ tracing enabled + fortio to generate traffic.

Version
1.1-rc0

Installation
helm init

Environment
gke

Cluster state