Description of problem: $gluster v stop gv1 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) n $gluster v delete gv1 Deleting volume will erase all information about the volume. Do you want to continue? (y/n) n Answer is No in both of the above. But event is sent.
REVIEW: http://review.gluster.org/15399 (eventsapi: Fix Volume Stop and delete prompt issue) posted (#1) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/15399 (eventsapi: Fix Volume Stop and delete prompt issue) posted (#2) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/15399 committed in master by Atin Mukherjee (amukherj) ------ commit f20e41aec392a45f860fa7e80ad5ee9d5607a45c Author: Aravinda VK <avishwan> Date: Mon Sep 5 11:15:10 2016 +0530 eventsapi: Fix Volume Stop and delete prompt issue During Volume Stop and Delete, event is emitted even if prompt answer is No. Also added "force" details in START and STOP events. BUG: 1373072 Change-Id: I986dcff7154b584f6ed44b533d4eeabe82815235 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/15399 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
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/