Bug 1723168 - Add CI test that checks that java exceptions are caught
Summary: Add CI test that checks that java exceptions are caught
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: General
Version: 4.3.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Aviv Litman
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On: 1673808
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-23 13:11 UTC by Shirly Radco
Modified: 2022-06-08 09:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-12 13:33:21 UTC
oVirt Team: Metrics
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-37973 0 None None None 2021-10-21 13:35:02 UTC

Description Shirly Radco 2019-06-23 13:11:00 UTC 
Description of problem:
We want to add a CI test  that verifies that java exceptions are caught by the ETL procees. This should be test also due top the fix to bug #1673808.

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

How reproducible:


Steps to Reproduce:
1. Stop the DWH process by a signal different then SIGTERM and SIGINT 
2. See that this is caught and reported to the engine audit log (/var/log/audit/audit.log)
3.

Actual results:


Expected results:
Java exception in the ETL process should be reported to the engine audit log.

Additional info:
Comment 1 Martin Perina 2021-10-21 13:19:52 UTC 
Is this feasible? Will we be able to cover all ETL flows?
Comment 4 Martin Perina 2022-05-12 13:33:21 UTC 
Closing as WORKSFORME, if the issue is still reproduced, feel free to reopen
Note You need to log in before you can comment on or make changes to this bug.