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:
Also this glusterfs process is a mount process ( mount.glusterfs ) which still runs on the node, even when the node is moved to maintenance
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?.
Ramesh, by not checking "stop glusterd service" option engine does not get unmounted.
Gluster mount process continues to run though unmount succeeded. Prasanna, can you take a look?
This bug is fixed in gluster as per the bugs listed in Depends list, no change required in oVirt. Closing this.