openshift-monitoring stack pods are in CrashLoopBackOff state with permission error
Issue
- Removed anyuid scc from openshift-monitoring pods
Refer this KCS : Prometheus and elasticsearch pods fails to start due wrong Security Context Constraints (SCC) - openshift-monitoring stack's Security Context Constraint group has been changed from anyuid to restricted.
- openshift-monitoring stack pods are in CrashLoopBackOff state with permission error while pods are restarting
#error message
standard_init_linux.go:178: exec user process caused "operation not permitted"
Environment
Openshift Container Platform 3.11
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.