Bug 1957031 - Fail CI jobs if there are core dumps present
Summary: Fail CI jobs if there are core dumps present
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: jamo luhrsen
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On: 1957030
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 21:43 UTC by Tim Rozet
Modified: 2022-08-26 14:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-26 14:14:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift release pull 20503 0 None open Bug 1957031: Move e2e-*-ovn to generated jobs 2021-07-22 20:51:30 UTC
Github openshift release pull 20566 0 None open Bug 1957031: Fail OVN jobs if core dumps are found 2021-07-23 19:47:13 UTC

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


Note You need to log in before you can comment on or make changes to this bug.