Bug 1531052

Summary:	glusterd not starting after node reboot
Product:	[oVirt] ovirt-host-deploy	Reporter:	Bernhard Seidl <info>
Component:	Plugins.Gluster	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, cshao, lsvaty, sabose
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2? sasundar: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	1.7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-host-deploy-1.7.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:23:48 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:
Bug Depends On:
Bug Blocks:	1478904

Description Bernhard Seidl 2018-01-04 13:25:38 UTC

Description of problem:
Glusterd is not started again automatically in an hyperconvergenced gluster setup after a graceful shutdown.

Version-Release number of selected component (if applicable):
ovirt-node-ng-installer-ovirt-4.2-2017122007


How reproducible:
100%

Steps to Reproduce:
1. Install a three node hyperconvergenced gluster setup
2. Graceful shutdown of cluster (see additional info) 
3. switch on all nodes

Actual results:
glusterd is not started by default

Expected results:
glusterd starts by default


Additional info:
Detailed Procedure to shutdown and start:
https://lists.ovirt.org/pipermail/users/2018-January/086062.html. However the startup procedure is missing a "Disable global ha maintenance" before "7. Start VMs".

Comment 1 SATHEESARAN 2018-05-10 02:41:27 UTC

Tested with RHV 4.2.3 and gluster-3.12
When the node is gracefully shutdown, glusterd comes up automagically on the next boot

Comment 2 Sandro Bonazzola 2018-05-10 06:23:48 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

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