Bug 1492061

Summary:	CLIENT_CONNECT event not being raised
Product:	[Community] GlusterFS	Reporter:	Darshan <dnarayan>
Component:	eventsapi	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.12	CC:	amukherj, avishwan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-glusterfs-3.12.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-13 12:46:24 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:
Embargoed:
Bug Depends On:	1492968
Bug Blocks:	1491574

Description Darshan 2017-09-15 11:23:53 UTC

Description of problem:
Not able to see CLIENT_CONNECT event. I see following log messages(events.log) when I try to simulate client connect event.
LOG:
------
[2017-09-15 16:07:02,129] WARNING [glustereventsd - 46:handle] - Unable to parse Event 1505471822 97 client_uid=dhcp43-199.lab.eng.blr.\
redhat.com-8075-2017/09/15-10:37:00:957322-rep_vol-client-0-0-0;client_identifier=10.70.43.199:49009;server_identifier=10.70.42.128:491\
61;brick_path=/root/bricks/rep_vol_B1,subdir_mount=(null)
------

Version-Release number of selected component (if applicable):
3.12

How reproducible:
Always

Steps to Reproduce:
1. killed few brick processes, for which I get "CLIENT_DISCONNECT" event
2. Force started the volume
3. I see the errors pasted above in events.log

Actual results:
CLIENT_CONNECT event not being raised

Expected results:
CLIENT_CONNECT event has to be raised when a client gets connected.

Additional info:

Comment 1 Worker Ant 2017-09-20 14:41:49 UTC

REVIEW: https://review.gluster.org/18330 (eventsapi: Fix issue with CLIENT_CONNECT event) posted (#1) for review on release-3.12 by Aravinda VK (avishwan)

Comment 2 Worker Ant 2017-10-05 12:00:26 UTC

COMMIT: https://review.gluster.org/18330 committed in release-3.12 by jiffin tony Thottan (jthottan) 
------
commit 33d030d12ff46f900b3d75375fa36983036ec160
Author: Aravinda VK <avishwan>
Date:   Tue Sep 19 09:39:31 2017 +0530

    eventsapi: Fix issue with CLIENT_CONNECT event
    
    A mismatch in event format causing below error in events.log when
    it detects CLIENT_CONNECT event.
    
        [2017-09-19 09:35:06,785] WARNING [glustereventsd - 46:handle] -
        Unable to parse Event 1505793906 97
        client_uid=f241-16363-2017/09/19-04:05:06:747558-gv1-client-
        0-0-0;client_identifier=192.168.122.208:49150;server_identifier=
        192.168.122.208:49152;brick_path=/bricks/b1,subdir_mount=(null)
    
    > Reviewed-on: https://review.gluster.org/18322
    > Reviewed-by: Atin Mukherjee <amukherj>
    > Smoke: Gluster Build System <jenkins.org>
    > Reviewed-by: Amar Tumballi <amarts>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Prashanth Pai <ppai>
    > (cherry picked from commit 23649f9ab73448737ee5d9509502f96e4775dca3)
    
    BUG: 1492061
    Change-Id: Ie6d507725a7e6b54fca44651f9c5e66eca2be244
    Signed-off-by: Aravinda VK <avishwan>

Comment 3 Jiffin 2017-10-13 12:46:24 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.12.2, please open a new bug report.

glusterfs-glusterfs-3.12.2 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-October/032684.html
[2] https://www.gluster.org/pipermail/gluster-users/