Bug 1957031

Summary: Fail CI jobs if there are core dumps present
Product: OpenShift Container Platform Reporter: Tim Rozet <trozet>
Component: NetworkingAssignee: jamo luhrsen <jluhrsen>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: high CC: bbennett, vlaad
Version: 4.7   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-26 14:14:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1957030    
Bug Blocks:    

Description Tim Rozet 2021-05-04 21:43:56 UTC
Description of problem:
Currently our periodic and pre-submit jobs run and unknowingly there could be core dumps where OVN crashed. We are seeing that in periodic upgrade jobs like:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade/1389623166254452736

We should have an e2e test that checks to see if there are cores after a run and then fail the test if so.

Comment 1 jamo luhrsen 2021-07-22 20:54:03 UTC
The first step was getting our normal e2e-*-ovn jobs to be generated jobs and not templated so they can use workflows where
we have a core dump step. that PR is here: https://github.com/openshift/release/pull/20503

Comment 2 jamo luhrsen 2021-09-01 18:29:07 UTC
the work to fail on core dumps wont be merged until we get the oustanding core dump resolved in glibc which is
tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1957030