-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14
-
None
-
Critical
-
None
-
False
-
Description of problem:
Installing OSSO 1.2.2 results in secondary-scheduler-operator pod going to crashLoopBackOff state. [knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc get pods -n openshift-secondary-scheduler-operator NAME READY STATUS RESTARTS AGE secondary-scheduler-operator-f49cb4b57-l64mf 0/1 CrashLoopBackOff 3 (21s ago) 2m47s [knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc logs -f secondary-scheduler-operator-f49cb4b57-l64mf -n openshift-secondary-scheduler-operator W1104 11:49:23.421788 1 cmd.go:237] Using insecure, self-signed certificates F1104 11:49:23.422145 1 cmd.go:162] mkdir /tmp/serving-cert-930427890: read-only file system
Version-Release number of selected component (if applicable):
[knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc get csv -n openshift-secondary-scheduler-operator NAME DISPLAY VERSION REPLACES PHASE secondaryscheduleroperator.v1.2.2 Secondary Scheduler Operator for Red Hat OpenShift 1.2.2 secondaryscheduleroperator.v1.1.2 Installing
How reproducible:
Always
Steps to Reproduce:
1. Install 4.14 ocp cluster 2. Install OSSO 1.2.2 3.
Actual results:
secondary scheduler operator pod goes into crashLoopBackOff state with the error as seen in the description
Expected results:
User should be able to install OSSO successfully.
Additional info: