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

Multus containers missing terminationMessagePolicy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 261

      Description of problem:

      One of the conformance tests checks for terminationMessagePolicy to have FallbackToLogsOnError value. Two multus pods do not have this parameter configured in all their containers:

pods/dhcp-daemon-64hxc containers[dhcp-daemon] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/dhcp-daemon-64hxc initContainers[dhcp-daemon-initialization] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/multus-7wjfz containers[kube-multus] must have terminationMessagePolicy="FallbackToLogsOnError"
pods/multus-7wjfz initContainers[install-container-network-plugins] must have terminationMessagePolicy="FallbackToLogsOnError"

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

       

      How reproducible:

       

      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: