Bug 1723168

Summary:	Add CI test that checks that java exceptions are caught
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Shirly Radco <sradco>
Component:	General	Assignee:	Aviv Litman <alitman>
Status:	CLOSED WORKSFORME	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.5	CC:	alitman, bugs, gdeolive, michal.skrivanek, mperina
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When the DWH process stopped by any signal the engine will be notified on several places: 1. on the engine: /var/log/audit/audit.log: it will appear as "SERVICE_STOP" 2. on the Administration Portal (webadmin): under 'Events' it will appear as 'ETL Service Stopped', if you can't see any 'ETL Service Started' event since then it means that DWH process is still inactive. 3. on the engine db: in 'audit_log' table it will appear in the 'log_type_name' column as 'DWH_STOPPED' and the 'message' column will be 'ETL Service Stopped'. you can order by log_type_name, log_time and see if it started or still inactive.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-12 13:33:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1673808
Bug Blocks:

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