Bug 1170631

Summary:	If connection to DB fails , the job that checks DisconnectDwh flag does not reconnect to engine db
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Shirly Radco <sradco>
Component:	ovirt-engine-dwh	Assignee:	Shirly Radco <sradco>
Status:	CLOSED ERRATA	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	bazulay, bugs, gklein, lsurette, melewis, rbalakri, Rhev-m-bugs, yeylon, ykaul, ylavi
Target Milestone:	ovirt-3.6.0-rc	Keywords:	ZStream
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	OVIRT 3.6.0-1 first release	Doc Type:	Bug Fix
Doc Text:	Previously, when the connection to the database failed the job that checked the 'DisconnectDwh' flag did not reconnect to the engine database and this meant that the ETL did not stop. Now, the job that checks the 'DisconnectDwh' flag keeps trying to connect to the database if the connection fails.	Story Points:	---
Clone Of:	1170501
Clones:	1181642 (view as bug list)		Environment:
Last Closed:	2016-03-09 21:22:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1170501, 1181616
Bug Blocks:	1181642

Description Shirly Radco 2014-12-04 13:44:14 UTC

+++ This bug was initially created as a clone of Bug #1170501 +++

Description of problem:
If connection to DB fails , the job that checks "DisconnectDwh" flag does not reconnect to engine db.

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

How reproducible:
100%

Steps to Reproduce:
1. Have engine, dwh running
2. Restart postgresql
3. Change value of "DisconnectDwh" to 1

Actual results:
The ETL does not stop

Expected results:
ETL should stop

Additional info:

Comment 3 errata-xmlrpc 2016-03-09 21:22:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0404.html