I can see incomplete traces without root span on a regular base

[juergenfl]

Bug Report

Which version of the demo you are using?
Release 1.12.0

Symptom

There are constantly incomplete traces without root span, first span is from service "frontendproxy" with operation "ingress". The span is showing the error/warning:

"invalid parent span IDs=f428f3c2873aab72; skipping clock skew adjustment"

What is the expected behavior?

Complete traces starting with a root span

What is the actual behavior?

Please describe the actual behavior experienced.

Reproduce

Could you provide the minimum required steps to resolve the issue you're seeing?

1. Deploy Demo App
2. Ensure Load Generator is working with default config
3. Identify trace without root span

We will close this issue if:

• The steps you provided are complex.
• If we can not reproduce the behavior you're reporting.

Additional Context

Please feel free to add any other context about the problem here.

Downloaded trace from Jaeger UI:

trace-wo-root-span.json

Screenshot of trace (using OCI APM):