-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
-
-
Important
Description of problem:
cluster-logging-operator pod can't run successfully due to wrong scc. --- # oc get pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-5bb5c65f69-czc62 0/1 CreateContainerConfigError 0 25h --- # oc get pods -oyaml cluster-logging-operator-5bb5c65f69-czc62 | grep -i scc openshift.io/scc: dynatrace-activegate --- Similar issue was issued in OCP 4.11.z as well.
Version-Release number of selected component (if applicable):
The affected version we noticed 4.12.24
How reproducible:
deleting the pod or upgrading the cluster can lead to this issue
Steps to Reproduce:
1. Delete or scale the pod, or upgrade the cluster. 2. check every operator's pod in the cluster as some will pass and some will fail.
Actual results:
cluster-logging-operator-5bb5c65f69-czc62 0/1 CreateContainerConfigError 0 25h
Expected results:
cluster-logging-operator-5bb5c65f69-czc62 1/1 Running 0 25h
Additional info:
1. The cluster is running on Azure 2. Installed using IPI --- The issue can be fixed by changing the priority of the SCC from 1 to 0, then delete the pod, the pod will use another SCC, then do the same until it uses the correct SCC. ---
- clones
-
-
- Closed
-