Repository navigation
[quarkus-next] TracingProviderTest.spanInfo fails due to OTel 1.60 W3C random trace flag #48552
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
dist/quarkus
Describe the bug
TracingProviderTest#spanInfo fails on quarkus-next after Quarkus PR #53476 bumped OTel SDK from 1.59.0 to 1.60.1.
OTel 1.60 implements W3C Trace Context Level 2 and now sets the "random" flag (0x02) on trace flags alongside the "sampled" flag (0x01).
This will become affecting Keycloak with Quarkus version 3.35.0.CR1, so it should not be merged to main sooner. Thus for now the fix targets quarkus-next branch only and will be cherry-picked later.
Version
nightly
Regression
- The issue is a regression
Expected behavior
Test expects getTraceFlags() to equal TraceFlags.getSampled() (01).
Actual behavior
Expected: is <01>
but: was <03>
getTraceFlags() returns 03 (sampled 0x01 + random 0x02).
https://github.com/keycloak/keycloak/actions/runs/25028049323/job/73304002137
How to Reproduce?
Run the test from quarkus-next:
mvn test -pl tests/base -Dtest="TracingProviderTest#spanInfo" -DfailIfNoTests=false
Anything else?
No response
Metadata
Metadata
Assignees
Labels
Type
Fields
No fields configured for bug.
Activity
Pepo48 commentedon Jun 2, 2026
Fix for this issue lives in the
quarkus-nextbranch. It is going to be part ofmainwith the next Quarkus LTS upgrade. The upgrade checklist can be found at #49549.Thus, I'm closing this issue as already resolved.