Problem: gluster volume delete causes the "post delete" glusterfind hook script to run. The "post delete" script mistakenly deletes the .keys directory under /var/lib/glusterd/glusterfind which may cause SSH keys to be deleted if there were glusterfind sessions created on the node. Although the issue has become evident as part of erasing RPMs, the problem is not related to packaging.
REVIEW: http://review.gluster.org/16052 (tools/glusterfind: avoid deleting keys directory) posted (#1) for review on master by Milind Changire (mchangir)
COMMIT: http://review.gluster.org/16052 committed in master by Aravinda VK (avishwan) ------ commit 2b4b928ed350286192b63b10b18f85c669b741f8 Author: Milind Changire <mchangir> Date: Wed Dec 7 17:27:02 2016 +0530 tools/glusterfind: avoid deleting keys directory Problem: gluster volume delete mistakenly deletes the .keys directory under /var/lib/glusterd/glusterfind. Solution: Check for ".keys" directory and avoid deleting it. Change-Id: Ia595c8bf3f423c1ad5d6faa183a29598c07a11f9 BUG: 1402369 Signed-off-by: Milind Changire <mchangir> Reviewed-on: http://review.gluster.org/16052 Reviewed-by: Aravinda VK <avishwan> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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/