Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1492968

Summary: CLIENT_CONNECT event is not notified by eventsapi
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: eventsapiAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: amukherj
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.13.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1492971 (view as bug list) Environment:
Last Closed: 2017-12-08 17:40:53 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:    
Bug Blocks: 1492061    

Description Aravinda VK 2017-09-19 04:16:14 UTC 
Description of problem:

CLIENT_CONNECT event is missed due to a mismatch in the events format. Following error is logged in events.log

[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)


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


How reproducible:
Always

Steps to Reproduce:
1. Setup Eventsapi listener
2. Create a volume and mount
3. All events will be displayed in dashboard but not CLIENT_CONNECT
Comment 1 Worker Ant 2017-09-19 04:17:30 UTC 
REVIEW: https://review.gluster.org/18322 (eventsapi: Fix issue with CLIENT_CONNECT event) posted (#1) for review on master by Aravinda VK (avishwan)
Comment 2 Worker Ant 2017-09-19 10:54:16 UTC 
COMMIT: https://review.gluster.org/18322 committed in master by Atin Mukherjee (amukherj) 
------
commit 23649f9ab73448737ee5d9509502f96e4775dca3
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)
    
    BUG: 1492968
    Change-Id: Ie6d507725a7e6b54fca44651f9c5e66eca2be244
    Signed-off-by: Aravinda VK <avishwan>
    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>
Comment 3 Shyamsundar 2017-12-08 17:40:53 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-3.13.0, please open a new bug report.

glusterfs-3.13.0 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/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/