Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto-instrumentation: can't preserve ownership of initcontainer volume #2617

Closed
leofvo opened this issue Feb 12, 2024 · 3 comments
Closed

auto-instrumentation: can't preserve ownership of initcontainer volume #2617

leofvo opened this issue Feb 12, 2024 · 3 comments
Labels
bug Something isn't working needs triage

Comments

@leofvo
Copy link

leofvo commented Feb 12, 2024

Component(s)

instrumentation

What happened?

Description

I using python auto-instrumentation in a kubernetes cluster. I have installed the operator and the instrumentation CRD (all up to date).
I have deployed about 6 services, all using fastapi. And one of my service isn't sending metrics and traces to my collector.
The collector is the same, operator same, same namespace and the instrument CR too.
image

Steps to Reproduce

Expected Result

Init container booting and finished without any issues..

Actual Result

When my pods is starting, the init container launch and this kind of error message appears:
cp: can't preserve ownership of '/otel-auto-instrumentation-python/./zipp-3.17.0.dist-info/top_level.txt': Operation not permitted

I can't get traces or metrics exported to my collector...

Here is a screenshot of the initcontainer logs:

image

Kubernetes Version

v1.28.5-eks-5e0fdde

Operator version

v0.93.0

Collector version

v0.90.1

Environment information

││     app.kubernetes.io/component: controller-manager
││     app.kubernetes.io/instance: opentelemetry-operator
││     app.kubernetes.io/managed-by: Helm
││     app.kubernetes.io/name: opentelemetry-operator
││     app.kubernetes.io/version: 0.93.0
││     argocd.argoproj.io/instance: observability
││     helm.sh/chart: opentelemetry-operator-0.47.0

Log output

No response

Additional context

No response

@leofvo leofvo added bug Something isn't working needs triage labels Feb 12, 2024
@leofvo
Copy link
Author

leofvo commented Feb 12, 2024

Duplicate issues due to network bug...

@leofvo leofvo closed this as completed Feb 12, 2024
@howan36
Copy link

howan36 commented Mar 3, 2024

what you have done to solve this issue

@leofvo
Copy link
Author

leofvo commented Mar 3, 2024

what you have done to solve this issue

Not solved for now, but this is a duplicate. Refer to: #2616

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

2 participants