-
Notifications
You must be signed in to change notification settings - Fork 111
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
callhome pod doesn't start: permission denied #1784
Comments
I think this is a |
Seems to be an issue with permissions. I created a sevice account that is allowed to run container as root and now I get this error:
But even when I add the cluster-admin role to the sa it doesn't work. As far as I understood the callhome container is for sending stats to you and to offer metrics that I can use with Prometrics, right? If I cannot access metrics here I would delete the deployment... |
For now you can disable it: |
Okay, so for now I will disable it and we can close this issue. Maybe you can bring this to development so that openEBS will work completely with OpenShift. |
Thanks, I'll leave this open so we can track it as a bug fix |
OpenEBS is running on an OpenShift cluster. Everything runs as expected except the callhome pod. I increased the loglevel and have a log file attached.
openebs-obs-callhome-6f47f84c55-dfbqw-obs-callhome (1).log
Short version, I get a permission denied:
But I don't get a clue where I should look or what I can do...
The text was updated successfully, but these errors were encountered: