Skip to content

revert: support new bee OTLP tracing flags (#585)#594

Closed
martinconic wants to merge 1 commit into
masterfrom
revert/otlp-tracing-flags-585
Closed

revert: support new bee OTLP tracing flags (#585)#594
martinconic wants to merge 1 commit into
masterfrom
revert/otlp-tracing-flags-585

Conversation

@martinconic
Copy link
Copy Markdown
Contributor

Reverts #585.

Why

PR #585 introduced tracing-otlp-endpoint, tracing-otlp-insecure, and tracing-sampling-ratio config keys in the rendered bee config (replacing tracing-endpoint). Bee master does not yet recognise those keys — the OpenTelemetry migration is on the feat/opentelemetry-migration branch and hasn't merged.

The mismatch causes every bee PR's Beekeeper / Integration tests job to fail: bee exits at startup with

Error: unknown parameters:
        tracing-otlp-endpoint
        tracing-otlp-insecure
        tracing-sampling-ratio

(verified via the kubectl_logs debug artifact from a failed run). Bee never becomes ready, the readiness probe times out, the cluster setup hits the 30-minute limit.

What this does

Plain git revert of 34f33e4 — restores tracing-endpoint in the BeeConfig struct, orchestration Config, k8s template, and the three cluster yamls.

Follow-up

Reopen #585 so it can re-land alongside the bee OpenTelemetry migration.

This reverts commit 34f33e4.

PR #585 introduced `tracing-otlp-endpoint`, `tracing-otlp-insecure`,
and `tracing-sampling-ratio` config keys in the bee config template,
replacing `tracing-endpoint`. Bee master does not yet recognise these
keys (the OpenTelemetry migration is on the `feat/opentelemetry-migration`
branch and hasn't merged), so bee fails startup with "unknown parameters"
and bee PR CI consistently times out at "bootnode-0 is not ready yet".

Revert until the bee OpenTelemetry migration lands; #585 will be
reopened so the change can re-land alongside it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant