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

Bug 1751299

Summary:	oVirt Engine restarts glusterd during host activation process even if it's already running
Product:	[oVirt] ovirt-engine	Reporter:	Daniel Milewski <daniel.milewski>
Component:	BLL.Gluster	Assignee:	Sahina Bose <sabose>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.4.3	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-18 07:35:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Milewski 2019-09-11 16:34:26 UTC

Description of problem:
In HC environments Engine attempts to restart glusterd when host is activated. It seems innocent but this behavior can make entire SD unavailable when a large fraction of hosts becomes non-responsive (in our case, because they couldn't reach another SD) and with Engine trying to autorecover them. By restarting too many glusterd instances at the same time it makes SD unavailable and moves VMs into paused state.

Version-Release number of selected component (if applicable):
4.3.4.3-1.el7

Additional info:
I found the code which does this at backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/ActivateVdsCommand.java. I believe it should attempt to start glusterd instead of restarting it.

Comment 1 Sahina Bose 2019-09-18 07:35:14 UTC


*** This bug has been marked as a duplicate of bug 1741102 ***