Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The bug description has no details here, what are we supposed to enhance? I am assigning this to nfs-ganesha component for further details and actions.
AFAIR I filed this bug to introduce force option for ganesha cli's. If somehow the option "nfs-ganesha" or vol set option "ganesha.enable" are inconsistent across the cluster, then there is no way come out of that state via cli. By introducing "force", the existing inconsistency can over writte.
Migrated to github: https://github.com/gluster/glusterfs/issues/568 Please follow the github issue for further updates on this bug.