The cluster-storage-operator pods do not provide a termination message, hindering debugging efforts when the pods are crash looping. At minimum, the pod's terminationMessagePolicy should be "FallbackToLogsOnError". See https://kubernetes.io/docs/tasks/debug-application-cluster/determine-reason-pod-failure/#customizing-the-termination-message Expected Results: The termination message should appear in a pod container's .status.lastState.terminated.message field.
Pushing this to 4.2. We could consider a fix in 4.1.z, but it doesn't seem worth blocking 4.1.0 for this.
PR opened: https://github.com/openshift/cluster-storage-operator/pull/33. agree it's not a blocker. No risk if we merge it early though.
$ oc get co storage NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE storage 4.2.0-0.nightly-2019-06-24-160709 True False False 56m $ oc get pods -n openshift-cluster-storage-operator -o yaml | grep -i termination terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError terminationGracePeriodSeconds: 30
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922