Bug 1386518

Summary: [Eventing]: SVC_DISCONNECTED event is not generating when bitd&scrub, quota and uss services are disabled
Product: Red Hat Gluster Storage Reporter: Byreddy <bsrirama>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED NOTABUG QA Contact: Byreddy <bsrirama>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: rhs-bugs, storage-qa-internal, vbellur
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: 2016-10-19 08:12:48 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:

Description Byreddy 2016-10-19 07:35:24 UTC
Description of problem:
=======================
SVC_DISCONNECTED event is not generating  when bitd&scrub, quota and uss  services are disabled

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.8.4-2

How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Have 2 node cluster
2. Have simple distribute volume running with 3 bricks
3. Setup to capture the gluster operation events
4. Enable the bitrot, quota and uss services for the volume
5. Now disable the above enabled services (step-4 )
6. Check SERVICE_DISCONNECTED event is generating when each service is disabled.

Actual results:
===============
SVC_DISCONNECTED event is not generating  when bitd&scrub, quota and uss services are disabled


Expected results:
=================
SVC_DISCONNECTED event should generate when services are disabled



Additional info:
================
When services are enabled, i am seeing SVC_CONNECTED events generating.

Comment 2 Atin Mukherjee 2016-10-19 08:12:48 UTC
If the services are disabled explicitly, we do not generate SVC_DISCONNECT event as the event will be generated from CLI itself. In case a daemon goes down abruptly, SVC_DISCONNECT will be generated.