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

CI does not provide failure details

    XMLWordPrintable

Details

    • Moderate
    • No
    • Hypershift Sprint 245, Hypershift Sprint 246
    • 2
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      Results of -hypershift-aws-e2e-external CI jobs do not contain obvious reason why a test failed. For example, this TestCreateCluster is listed as failed, but all failures in TestCreateCluster look like errors dumping the cluster after failure.

      It should show that "storage operator did not become Available=true". Or even tell that "pod cluster-storage-operator-6f6d69bf89-fx2d2 in the hosted control plane XYZ is in CrashloopBackoff"

      The PR under test had a simple typo leading to crashloop and it should be more obvious what went wrong.

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

      4.15.0-0.ci.test-2023-10-03-040803

       

      Attachments

        Activity

          People

            pstefans@redhat.com Patryk Stefanski
            rhn-engineering-jsafrane Jan Safranek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: