Description of problem: Unexport of volume via gluster cli will fail if export configuration file is not present. Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: 1. export a volume via gluster v set <volname> ganesha.enable on 2. delete export configuration file 3. try to unexport gluster v set <volname> ganesha.enable off Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/16771 (ganesha/scripts : remove dependency over export configuration file for unexport) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/16771 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit 05dca214324ea252dff1403e2571f6811b91f550 Author: Jiffin Tony Thottan <jthottan> Date: Thu Feb 23 16:21:52 2017 +0530 ganesha/scripts : remove dependency over export configuration file for unexport Currently unexport is performed by reading export id from volume configuration file. So unexport has dependency over that file. This patch will unexport with help of dbus command ShowExport. And it will only unexport the share which is added via cli. Change-Id: I6f3c9b2bb48f0328b18e9cc0e4b9356174afd596 BUG: 1427079 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/16771 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Raghavendra Talur <rtalur>
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.2, please open a new bug report.