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

[CI] Job success criteria flawed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.20.0
    • Windows Containers
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 0
    • None
    • None
    • None
    • None
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-62480. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-60967. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-60771. The following is the description of the original issue:
      —
      Description of problem:

          In CI We are reporting jobs as failed if a pod within the job failed. This is incorrect logic, as a single pod failing is not a failure state for the entire job. The job will keep creating pods until a success is seen.

This causes various CI issues such as https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_windows-machine-config-operator/3198/pull-ci-openshift-windows-machine-config-operator-master-vsphere-disconnected-e2e-operator/1958356839347261440

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

      How reproducible:

          N/A

      Steps to Reproduce:

      N/A

      Actual results:

          N/A

      Expected results:

          N/A

      Additional info:

              team-winc Team WinC
              rh-ee-ssoto Sebastian Soto
              None
              None
              Aharon Rasouli Aharon Rasouli
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: