Error about invalid argument "-component.UseLocalHostAsDefaultHost" #35569
Labels
Comments
odubajDT
added
bug
This was referenced Oct 3, 2024
mx-psi
pushed a commit
that referenced
this issue
Oct 3, 2024
…able (#35570) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Move -component.UseLocalHostAsDefaultHost feature gate to stable to be aligned with the Otel-collector [core repository components](https://github.com/open-telemetry/opentelemetry-collector/pull/11235/files#diff-aa3f33da15c55657195189f2f092ca32a6d9f17d9f4ba450041f88e1bdcc7711) **Link to tracking Issue:** #35569 --------- Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
jriguera
pushed a commit
to springernature/opentelemetry-collector-contrib
that referenced
this issue
Oct 4, 2024
…able (open-telemetry#35570) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Move -component.UseLocalHostAsDefaultHost feature gate to stable to be aligned with the Otel-collector [core repository components](https://github.com/open-telemetry/opentelemetry-collector/pull/11235/files#diff-aa3f33da15c55657195189f2f092ca32a6d9f17d9f4ba450041f88e1bdcc7711) **Link to tracking Issue:** open-telemetry#35569 --------- Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
ghost
pushed a commit
to sematext/opentelemetry-collector-contrib
that referenced
this issue
Oct 9, 2024
…able (open-telemetry#35570) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Move -component.UseLocalHostAsDefaultHost feature gate to stable to be aligned with the Otel-collector [core repository components](https://github.com/open-telemetry/opentelemetry-collector/pull/11235/files#diff-aa3f33da15c55657195189f2f092ca32a6d9f17d9f4ba450041f88e1bdcc7711) **Link to tracking Issue:** open-telemetry#35569 --------- Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
No response
What happened?
Description
With the latest release (v0.110.0), I get the following error in all OTel collector pods when deploying with the OpenTelemetry Operator:
The problem is the inconsistency of the state of the feature gate, since in the
opentelemetry-collectorcore repository, the state of the gate was moved to stable here. But in this repository, it's still in betaSteps to Reproduce
start the Otel collector with the "-component.UseLocalHostAsDefaultHost" feature gate
Expected Result
No error
Actual Result
Collector version
v0.110.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: