Description of problem: ----------------------- 4 node cluster. Do not create ganesha.conf and ganesha-ha.conf inside shared storage. Run gluster nfs-ganesha enable. The command shows "success". It would be good to have some sort of a validation check to check presence of these files.ATM,the success message on the CLI is misleading. [root@gqas013 ~]# gluster nfs-ganesha enable --mode=script This will take a few minutes to complete. Please wait .. nfs-ganesha : success [root@gqas013 ~]# [root@gqas013 ~]# ll /var/run/gluster/shared_storage/nfs-ganesha total 0 [root@gqas013 ~]# [root@gqas013 ~]# pcs status Error: cluster is not currently running on this node [root@gqas013 ~]# Version-Release number of selected component (if applicable): ------------------------------------------------------------- nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-4.el7rhgs.x86_64 How reproducible: ----------------- Always. Steps to Reproduce: ------------------- Given in description. Actual results: -------------- ganesha enable shows "success" on CLI,which isn't really the case. Expected results: ------------------ Ganesha enable should throw some sort of a meaningful message on CLI,post validation. Additional info: ---------------- -