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

Failing 40_microshift_running_check.sh (greenboot healthcheck for microshift) doesn't provide enough information about the failure

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.14
    • None
    • None
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 237, uShift Sprint 238, uShift Sprint 239

      Description of problem:

      When 40_microshift_running_check.sh fails, it doesn't say where the problem was specifically: it prints out that all namespaces are checked for pod restart, but when some fails it just prints FAILURE without any context

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      script output
      
      Checking pod restart count in the 'openshift-ovn-kubernetes' namespace
      Checking pod restart count in the 'openshift-service-ca' namespace
      Checking pod restart count in the 'openshift-ingress' namespace
      Checking pod restart count in the 'openshift-dns' namespace
      Checking pod restart count in the 'openshift-storage' namespace
      FAILURE

      Expected results:

      Script prints information about which namespace/pod failed and why (what condition was unfulfilled, like ratio between samples with and without restarts).
      Maybe time needed for this check can be extended since it's running in parallel now

      Additional info:

       

              ggiguash@redhat.com Gregory Giguashvili
              pmatusza@redhat.com Patryk Matuszak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: