-
Bug
-
Resolution: Done
-
Major
-
None
-
4.20.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
WINC - Sprint 276
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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:
- blocks
-
OCPBUGS-60967 [CI] Job success criteria flawed
-
- Closed
-
- is cloned by
-
OCPBUGS-60967 [CI] Job success criteria flawed
-
- Closed
-
- links to