Description of problem: Add support for running refresh config in ganesha environment. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Content from ganesha document: To modify the default export configurations perform the following steps on any of the nodes in the existing ganesha cluster: Edit/add the required fields in the corresponding export file located at /etc/ganesha/exports/. Execute the following command: # /usr/libexec/ganesha/ganesha-ha.sh --refresh-config <HA_CONF_DIR> <volname> where, HA_CONF_DIR: The directory path containing the ganesha-ha.conf file. By default it is located at /etc/ganesha. volname: The name of the volume whose export configuration has to be changed. For example: # /usr/libexec/ganesha/ganesha-ha.sh --refresh-config /etc/ganesha testvol Actual results: Expected results: To have support for refresh config in ganesha environment. Additional info:
Commit: https://github.com/gluster/gdeploy/commit/5752f74 fixes the issue.
Rebase fixes the issue.
Verified this Bug on gdeploy-2.0.1-5.el7rhgs.noarch glusterfs-3.8.4-5.el7rhgs.x86_64 For now Refresh Config support has been added in Gdeploy. While verifying this raised few bugs for refresh config related to adding 2 or more client permissions,Modifying existing client permissions,Deleting client permission from export block: https://bugzilla.redhat.com/show_bug.cgi?id=1397738 https://bugzilla.redhat.com/show_bug.cgi?id=1397743 https://bugzilla.redhat.com/show_bug.cgi?id=1397750 As the refresh config support has been added to gdeploy,Hence marking this bug as verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2017-0482.html