Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1233033 - nfs-ganesha: ganesha-ha.sh --refresh-config not working
nfs-ganesha: ganesha-ha.sh --refresh-config not working
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nfs-ganesha (Show other bugs)
3.1
x86_64 Linux
high Severity urgent
: ---
: RHGS 3.1.0
Assigned To: Meghana
Saurabh
:
: 1233582 (view as bug list)
Depends On:
Blocks: 1202842 1233624 1235258
  Show dependency treegraph
 
Reported: 2015-06-18 02:02 EDT by Saurabh
Modified: 2016-01-19 01:14 EST (History)
6 users (show)

See Also:
Fixed In Version: glusterfs-3.7.1-6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1233624 (view as bug list)
Environment:
Last Closed: 2015-07-29 01:05:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description Saurabh 2015-06-18 02:02:42 EDT
Description of problem:
As part of ganesha-ha setup we have a script called ganesha-ha.sh. This script is used to setting up the cluster and update the running nfs-ganesha process if any modifications are done in the configuration files.
Command used for updating the nfs-ganesha process is ganesha-ha.sh --refresh-config and this is not working.

Version-Release number of selected component (if applicable):
glusterfs-3.7.1-3.el6rhs.x86_64
nfs-ganesha-2.2.0-3.el6rhs.x86_64

How reproducible:
always

Actual results:
refresh-config is not working as desired,

Expected results:
refresh config should be able to update the nfs-ganesha about the modifications done and nfs-ganesha therefore should work based on the modifications done in config files

Additional info:
Comment 2 Meghana 2015-06-19 05:39:51 EDT
*** Bug 1233582 has been marked as a duplicate of this bug. ***
Comment 5 Saurabh 2015-07-05 07:11:00 EDT
based on the test that I did to check the functionality I found that all the export files were modified on all nodes post execution of this command. The ganesha process was updated and mount worked accordingly.

[root@rhsauto009 ~]# mount -t nfs -o vers=3 10.70.44.96:/vol2 /mnt

[root@rhsauto009 ~]# touch  /mnt/lock_test
touch: cannot touch `/mnt/lock_test': Read-only file system

[root@rhsauto009 ~]# umount /mnt

[root@rhsauto009 ~]# mount -t nfs -o vers=4 10.70.44.96:/vol2 /mnt

[root@rhsauto009 ~]# touch  /mnt/lock_test
touch: cannot touch `/mnt/lock_test': Read-only file system

[root@rhsauto009 ~]# cat  /mnt/locks_test
======================st écrite par le maitre dans le fichier[root@rhsauto009 ~]# 

[root@rhsauto009 ~]#
Comment 6 errata-xmlrpc 2015-07-29 01:05:49 EDT
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/RHSA-2015-1495.html

Note You need to log in before you can comment on or make changes to this bug.