Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-3154

Topolvm pods lack termination message policy

XMLWordPrintable

    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • 1
    • uShift Sprint 253
    • Low

      Description of problem:

      From OCP conformance:
pods/topolvm-controller-7b5ccd6c84-tfrzs containers[csi-provisioner] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-controller-7b5ccd6c84-tfrzs containers[csi-resizer] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-controller-7b5ccd6c84-tfrzs containers[csi-snapshotter] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-controller-7b5ccd6c84-tfrzs containers[liveness-probe] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-controller-7b5ccd6c84-tfrzs containers[topolvm-controller] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-controller-7b5ccd6c84-tfrzs initContainers[self-signed-cert-generator] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-node-vr6f2 containers[csi-registrar] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-node-vr6f2 containers[liveness-probe] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-node-vr6f2 containers[topolvm-node] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/topolvm-node-vr6f2 initContainers[file-checker] must have terminationMessagePolicy="FallbackToLogsOnError"

      Version-Release number of selected component (if applicable):

      4.16

      How reproducible:

      Run conformance tests.

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

              pacevedo@redhat.com Pablo Acevedo Montserrat
              pacevedo@redhat.com Pablo Acevedo Montserrat
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: