Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168160

Summary:	engine-setup does not reset DisconnectDwh on failure
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yedidyah Bar David <didi>
Component:	ovirt-engine-setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	bazulay, ecohen, gklein, iheim, lsurette, rbalakri, Rhev-m-bugs, sbonazzo, scohen, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	org.ovirt.engine-root-3.5.0-23	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-12 14:15:04 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:

Description Yedidyah Bar David 2014-11-26 10:02:47 UTC

Description of problem:

If engine-setup tries to disconnect a remote dwhd by setting DisconnectDwh to 1, it does not set it back to 0 on failure. Next attempts to start dwhd will then fail (currently silently, see bug 1168141).

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

How reproducible:

always

Steps to Reproduce:
1. setup engine on macine A and dwh on machine B, start both
2. somehow prevent dwh access to engine db (e.g. firewall)
3. run engine-setup on A, it will try to stop dwh and fail
4. allow access of dwh to engine db (revert step 2)
5. try to restart dwh

Actual results:

dwh fails to start

Expected results:

success

Additional info:

step 2 is currently "happening" also due to bug 1167801 .

Comment 1 Yedidyah Bar David 2014-11-26 10:03:41 UTC

Workaround: manually set it to 0 by running on engine db:

update vdc_options set option_value='0' where option_name = 'DisconnectDwh';