fix(containers): tolerate OTel bootstrap conflicts when backfilling old releases#6063
Merged
Merged
Conversation
opentelemetry-bootstrap -a install selects the latest per-library
instrumentation packages. When backfilling an older release, those
latest packages conflict with the release's pinned dependencies and the
build fails, e.g.:
RuntimeError: Dependency conflict found:
opentelemetry-instrumentation-openai-v2 2.4b0 requires
opentelemetry-util-genai>=0.4b0.dev, but you have 0.2b0
The base opentelemetry-distro/exporter install is still required, but the
per-library bootstrap is inherently best-effort. Add an OTEL_BEST_EFFORT
build arg: when set to 1, a bootstrap failure is logged and tolerated;
otherwise it remains fatal.
The publish workflow sets OTEL_BEST_EFFORT=1 only when bundling a
non-ogx package (a pre-rename backfill), so ogx release images keep the
strict behavior.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Charlie Doern <cdoern@redhat.com>
cdoern
requested review from
bbrowning,
franciscojavierarceo,
leseb,
mattf,
raghotham and
skamenan7
as code owners
franciscojavierarceo
approved these changes
Jun 8, 2026
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an
OTEL_BEST_EFFORTbuild arg. When set to1, a failure ofopentelemetry-bootstrap -a installis logged and tolerated instead of failing the image build. The baseopentelemetry-distro/opentelemetry-exporter-otlpinstall remains required either way.The publish workflow sets
OTEL_BEST_EFFORT=1only when bundling a non-ogxpackage (a pre-rename backfill, e.g.llama-stack).ogxrelease images keep the strict behavior.Why
opentelemetry-bootstrap -a installauto-selects the latest per-library instrumentation packages. When backfilling an older release, those conflict with the release's pinned deps and the build fails:Hit while backfilling
llama-stack0.5.2 images. The per-library bootstrap is inherently best-effort; the core OTel exporter/distro (the part needed for OTLP export) still installs.Effect
ogxrelease builds: unchanged — bootstrap stays strict (fatal on conflict).package_name != ogx): if the latest auto-instrumentation packages can't be installed cleanly, the image is built without that per-library auto-instrumentation, but with the base OTel exporter/distro intact.OTEL_*-triggeredopentelemetry-instrumentstill works; some library-specific spans may be missing.Test plan
pypi.ymlvalidated as YAML.ogx→ strict,llama-stack→ best-effort) and the bootstrap-failure branch logic.🤖 Generated with Claude Code