Description of problem: ----------------------- Vol stop fails when another gluster operstion,say rebalance is running(which is expected). But the volume stop unexports the volume on localhost before it fails on CLI. It'd be good to do the "unexport" part at the end of the Staging process. Version-Release number of selected component (if applicable): ------------------------------------------------------------- nfs-ganesha - 2.4.1.-6 How reproducible: ----------------- 100% Steps to Reproduce: ------------------- 1. Trigger rebalance 2. Stop the volume exported via Ganesha 3. Check showmount on localhots Actual results: --------------- The volume gets unexportd. Expected results: ----------------- Volume should not get unexported. Additional info: ---------------- More details in https://bugzilla.redhat.com/show_bug.cgi?id=1415630 .The issue was uncovered during that scenario.
Hi Soumya, I have edited the doc text for the release notes, but i need a little more clarity wrt the second sentence "the volume gets unexported in the node where the command is executed, but node still have volume being exported"
Hi Bhavana, I made few updates to the doc text. Please check the same - >>> If "gluster volume stop" operation on a volume exported via NFS-ganesha server fails, there is a probability that the volume shall get unexported on few nodes in spite of the command failure. This shall lead to inconsistent state across the NFS-ganesha cluster. Workaround: To restore the cluster back to normal state, perform the following - * identify the nodes where in the volume got unexported * re-export the volume manually using the below dbus command - # dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.AddExport string:/var/run/gluster/shared_storage/nfs-ganesha/exports/export.<volname>.conf string:"EXPORT(Path=/<volname>)" <<<
Thanks Soumya. Slightly edited the doc text for the release notes.