Bug 1330975

Summary:	glusterfs process does not stop on the node which is put into maintenance with "stop glusterd service" checked from UI
Product:	[oVirt] ovirt-engine	Reporter:	RamaKasturi <knarra>
Component:	BLL.Gluster	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED UPSTREAM	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.6.4	CC:	bugs, knarra, prasanna.kalever, sabose
Target Milestone:	ovirt-3.6.7	Flags:	sabose: ovirt-3.6.z? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1334620 (view as bug list)		Environment:
Last Closed:	2016-05-30 12:10:16 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:
Bug Depends On:	1331938, 1334750, 1335726
Bug Blocks:	1258386

Description RamaKasturi 2016-04-27 11:40:47 UTC

Description of problem:
when a host is put into maintenance with "stop glusterd service" it should stop all the glusterd, glusterfsd and glusterfs services. But this does not stop glusterfs services on the node.

Version-Release number of selected component (if applicable):
libgovirt-0.3.3-1.el7_2.1.x86_64
ovirt-host-deploy-1.4.1-1.el7ev.noarch
ovirt-vmconsole-1.0.0-1.el7ev.noarch
ovirt-vmconsole-host-1.0.0-1.el7ev.noarch
ovirt-setup-lib-1.0.1-1.el7ev.noarch
ovirt-hosted-engine-ha-1.3.5.1-1.el7ev.noarch
ovirt-hosted-engine-setup-1.3.4.0-1.el7ev.noarch


How reproducible:
Always

Steps to Reproduce:
1. Select one host which you want to move to maintenance. 
2. click on maintenance button.
3. select "stop glusterd service" and click "ok"

Actual results:
glusterfsd and glusterd services gets stopped but not glusterfs.

Expected results:
All glusterfsd, glusterd and glusterfs process should be stopped on the node.

Additional info:

Comment 1 SATHEESARAN 2016-04-27 11:42:48 UTC

Also this glusterfs process is a mount process ( mount.glusterfs ) which still runs on the node, even when the node is moved to maintenance

Comment 2 Ramesh N 2016-04-28 04:08:18 UTC

Gluster mount processes are not handled with "stop glusterd service" option. "stop glusterd service" which we have introduced recently helps to stop all gluster server side processes. But this mounts are on the client side. Actually vdsm supposed to unmount all the storages during host maintenance ( regardless of "stop glusterd service" option). I am not sure why that didn't happened. 

Kasturi, Can you check once again without checking "stop glusterd service"  option?.

Comment 3 RamaKasturi 2016-04-28 10:34:39 UTC

Ramesh, by not checking "stop glusterd service" option engine does not get unmounted.

Comment 5 Sahina Bose 2016-05-03 07:15:51 UTC

Gluster mount process continues to run though unmount succeeded. Prasanna, can you take a look?

Comment 6 Sahina Bose 2016-05-30 12:10:16 UTC

This bug is fixed in gluster as per the bugs listed in Depends list, no change required in oVirt. Closing this.