The cluster-node-tuning-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.
Ditto for the tuned pod.
https://github.com/openshift/cluster-node-tuning-operator/pull/51
https://github.com/openshift/cluster-node-tuning-operator/pull/51 merged
Verified on: 4.1.0-0.nightly-2019-05-14-202907 # oc get deployment cluster-node-tuning-operator -o yaml | grep terminationMessagePolicy terminationMessagePolicy: FallbackToLogsOnError
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:0758