Description of problem: This RFE is to track the changes required in the protocol server component to generate the events to be consumed by the eventing framework.
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#1) for review on master by Prasanna Kumar Kalever (pkalever)
*** This bug has been marked as a duplicate of bug 1369402 ***
*** Bug 1369402 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#2) for review on master by Prasanna Kumar Kalever (pkalever)
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#3) for review on master by Prasanna Kumar Kalever (pkalever)
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#4) for review on master by Prasanna Kumar Kalever (pkalever)
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#5) for review on master by Prasanna Kumar Kalever (pkalever)
REVIEW: http://review.gluster.org/15294 (protocol-server: generate events) posted (#6) for review on master by Prasanna Kumar Kalever (pkalever)
COMMIT: http://review.gluster.org/15294 committed in master by Raghavendra G (rgowdapp) ------ commit db3286184a1ab89d3edb9cf4d645a2db724fada0 Author: Prasanna Kumar Kalever <prasanna.kalever> Date: Tue Aug 30 13:40:41 2016 +0530 protocol-server: generate events This patch add/generate the events seen from/in the protocol server side, which will be consumed by the new eventing framework. ------------------------------------------------------------------------- | event | description | |-------------------------------|---------------------------------------| | EVENT_CLIENT_CONNECT | new client connected | |-------------------------------|---------------------------------------| | EVENT_CLIENT_AUTH_REJECT | client cannot be authenticated | |-------------------------------|---------------------------------------| | EVENT_CLIENT_DISCONNECT | client had disconnected | ------------------------------------------------------------------------- Thanks to "Raghavendra Talur" <rtalur> for all the help Change-Id: I4fda83fae7747507f64d81a7645cc3a8a2fbaeae BUG: 1369403 Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever> Reviewed-on: http://review.gluster.org/15294 Tested-by: Prasanna Kumar Kalever <pkalever> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp>
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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/