Description of problem: AFR_SUBVOL_UP and AFR_SUBVOLS_DOWN events not working. Version-Release number of selected component (if applicable): 3.12 How reproducible: Always Steps to Reproduce: 1. create a 1 X 2 replica volume. 2. kill both the bricks. 3. wait for AFR_SUBVOLS_DOWN event Actual results: These 2 events are not being raised Expected results: subvol up/down events must be sent whenever a subvolume goes up or down. Additional info: Looks these events are not being raised in the code. I see the event names only in events/eventskeygen.py file.
Assigning to Karthik who has agreed to send the fix.
REVIEW: https://review.gluster.org/18337 (cluster/afr: Sending subvol up/down events when subvol comes up or goes down) posted (#1) for review on release-3.12 by Karthik U S (ksubrahm)
COMMIT: https://review.gluster.org/18337 committed in release-3.12 by jiffin tony Thottan (jthottan) ------ commit 94faf8c4a1f5a020593ca65f44d68e1ba2f632eb Author: karthik-us <ksubrahm> Date: Wed Sep 20 18:30:21 2017 +0530 cluster/afr: Sending subvol up/down events when subvol comes up or goes down > BUG: 1493539 (cherry picked from commit 3bbb4fe4b33dc3a3ed068ed2284077f2a4d8265a) Change-Id: I6580351b245d5f868e9ddc6a4eb4dd6afa3bb6ec BUG: 1492066 Signed-off-by: karthik-us <ksubrahm>
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/