Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-48186

A monitor test should catch a panic in a system process

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.19.0
    • Node / CRI-O
    • Low
    • None
    • OCP Node Sprint 267 (Green), OCP Node Sprint 268 (Green)
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          in the fallout of https://github.com/openshift/machine-config-operator/pull/4765 which caused a CRI-O panic, TRT team needed to dig through node logs to find what process was failing. A test should catch a panic of CRI-O and Kubelet and report which node and process it happened on.

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

      How reproducible:

          100%

      Steps to Reproduce:

          1. create a segfault in kubelet or cri-o

      Actual results:

          sometimes the test may pass, if the node doesn't go NotReady

      Expected results:

          the tests should fail and catch this case

      Additional info:

              rh-ee-pbhojara Pannaga Rao Bhoja Ramamanohara
              pehunt@redhat.com Peter Hunt
              Cameron Meadors Cameron Meadors
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: