Description of problem: Stale export entries in ganesha.conf in shared storage after executing "gluster nfs-ganesha disable" Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: stale entries in ganesha.conf Expected results: entries should be removed Additional info:
REVIEW: https://review.gluster.org/16708 (ganesha/scripts : Remove export entries from ganesha.conf during cleanup) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
REVIEW: https://review.gluster.org/16708 (ganesha/scripts : Remove export entries from ganesha.conf during cleanup) posted (#2) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/16708 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit ad1d35239219a004358c37895d1f1dc1643acb1f Author: Jiffin Tony Thottan <jthottan> Date: Wed Feb 22 14:37:04 2017 +0530 ganesha/scripts : Remove export entries from ganesha.conf during cleanup Change-Id: I288f7c9ced23d258a7ce1242d8efe03a4bf6f746 BUG: 1425726 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/16708 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> Reviewed-by: Kaleb KEITHLEY <kkeithle>
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.