Bug 1233033

Summary:	nfs-ganesha: ganesha-ha.sh --refresh-config not working
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Saurabh <saujain>
Component:	nfs-ganesha	Assignee:	Meghana <mmadhusu>
Status:	CLOSED ERRATA	QA Contact:	Saurabh <saujain>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	kkeithle, mmadhusu, mzywusko, nlevinki, rcyriac, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.1-6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1233624 (view as bug list)		Environment:
Last Closed:	2015-07-29 05:05:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1202842, 1233624, 1235258

Description Saurabh 2015-06-18 06:02:42 UTC

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 09:39:51 UTC

*** Bug 1233582 has been marked as a duplicate of this bug. ***

Comment 5 Saurabh 2015-07-05 11:11:00 UTC

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 05:05:49 UTC

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