+++ This bug was initially created as a clone of Bug #1419816 +++ Description of problem: Refresh config fails, if any one or more nodes in ganesha cluster is in failover state Version-Release number of selected component (if applicable): nfs-ganesha-gluster-2.4.1-7.el7rhgs.x86_64 nfs-ganesha-2.4.1-7.el7rhgs.x86_64 nfs-ganesha-debuginfo-2.4.1-7.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-13.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a 4 node ganesha cluster. 2. Create a volume and enable ganesha on it. 3. Stop nfs-ganesha service in node2 and let failover happen. 4. Run Refresh config for the volume. Actual results: Refresh config fails on the node for which failover happened and it is not getting executed on the other nodes Expected results: If any one or more nodes in ganesha cluster is in failover state, refresh config should succeed on the other nodes in ganesha cluster. Additional info: Similar issue can happen for volume export/unexport
REVIEW: https://review.gluster.org/17081 (ganesha : allow refresh-config and volume export/unexport in failover state) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
REVIEW: https://review.gluster.org/17081 (ganesha : allow refresh-config and volume export/unexport in failover state) posted (#2) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/17081 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit e91cdf4d63893c3cc5506f8fd73f00dc47272dc6 Author: Jiffin Tony Thottan <jthottan> Date: Wed Apr 19 16:12:10 2017 +0530 ganesha : allow refresh-config and volume export/unexport in failover state If ganesha is not running on one of nodes in HA cluster, then alli dbus commands send to that ganesha server will fail. This results in both refresh-config and volume export/unepxort failure. This change will gracefully handle those scenarios. Change-Id: I3f1b7b7ca98e54c273c266e56357d8e24dd1b14b BUG: 1443490 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/17081 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>
REVIEW: https://review.gluster.org/17152 (ganesha : minor improvments for commit e91cdf4 (17081)) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
REVIEW: https://review.gluster.org/17152 (ganesha : minor improvments for commit e91cdf4 (17081)) posted (#2) for review on release-3.10 by jiffin tony Thottan (jthottan)
REVIEW: https://review.gluster.org/17152 (ganesha : minor improvments for commit e91cdf4 (17081)) posted (#3) for review on release-3.10 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/17152 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit 568d81673a5c1b21dd536d055fb6f94c8df0a7cd Author: Jiffin Tony Thottan <jthottan> Date: Wed May 3 12:47:14 2017 +0530 ganesha : minor improvments for commit e91cdf4 (17081) Change-Id: I3af13e081c5e46cc6f2c132e7a5106ac3355c850 BUG: 1443490 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/17152 Smoke: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> 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.