-
Bug
-
Resolution: Done
-
Undefined
-
rhosdt-3.6
-
Tracing Sprint # 279
-
Moderate
Description:
"fsnotify: can't remove non-existent watch" errors are streaming in OpenTelemetryCollector pods. Impact to the entire tracing system is not seen, everything is working fine but the errors are flooded.
Version:
Red Hat Builf of OpenTelemetry Operator v0.127.0-2
Repetitive Logs:
2025-09-11T09:36:02.841Z error bearertokenauthextension@v0.127.0/bearertokenauth.go:131 fsnotify: can't remove non-existent watch: /var/run/secrets/kubernetes.io/serviceaccount/token {"resource": {}, "otelcol.component.id": "bearertokenauth", "otelcol.component.kind": "extension"} github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension.(*BearerTokenAuth).startWatcher github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension@v0.127.0/bearertokenauth.go:131
Steps to reproduce:
The issue was not reproducible but the collector pod is flooded with above said errors, though the traces can be queried without any problems.
- links to
