Bug 1406330

Summary: [GANESHA] Extra hostname directory of the newly added node is created in /var/lib/nfs/ganesha/ on new node
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Manisha Saini <msaini>
Component: common-haAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED WONTFIX QA Contact: Manisha Saini <msaini>
Severity: unspecified Docs Contact:
Priority: low    
Version: rhgs-3.2CC: rhs-bugs, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-21 12:57:05 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:

Description Manisha Saini 2016-12-20 09:51:01 UTC
Description of problem:

When a node is added to the existing ganesha cluster,
hostname directory (of new node) having symlink from /var/lib/nfs/ganesha/dhcp46-219.lab.eng.blr.redhat.com -> 
/var/run/gluster/shared_storage/nfs-ganesha/dhcp46-219.lab.eng.blr.redhat.com/nfs/ganesha is created on the already exising nodes.

And the new node should have hostname directory of the other existing node.
But an extra directory of the node hostname itself and an extra ganesha dir is created on the new node.
A cleanup is required to remove this extra directory from new node

Version-Release number of selected component (if applicable):

rpm -qa | grep ganesha
nfs-ganesha-2.4.1-3.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.1-3.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-9.el7rhgs.x86_64


How reproducible:
Consistently

Steps to Reproduce:
1.Create 4 node ganesha cluster and enable ganesha on it
2.Add a node to existing cluster
/usr/libexec/ganesha/ganesha-ha.sh --add /var/run/gluster/shared_storage/nfs-ganesha/ dhcp47-59.lab.eng.blr.redhat.com 10.70.44.157

Node 1:
[root@dhcp46-219 ganesha]# ls
dhcp46-241.lab.eng.blr.redhat.com  dhcp47-45.lab.eng.blr.redhat.com  v4old
dhcp47-3.lab.eng.blr.redhat.com    dhcp47-59.lab.eng.blr.redhat.com  v4recov

Node 2:
[root@dhcp46-241 ganesha]# ls
dhcp46-219.lab.eng.blr.redhat.com  dhcp47-45.lab.eng.blr.redhat.com  v4old
dhcp47-3.lab.eng.blr.redhat.com    dhcp47-59.lab.eng.blr.redhat.com  v4recov

Node 3:
[root@dhcp47-3 ganesha]# ls
dhcp46-219.lab.eng.blr.redhat.com  dhcp47-45.lab.eng.blr.redhat.com  v4old
dhcp46-241.lab.eng.blr.redhat.com  dhcp47-59.lab.eng.blr.redhat.com  v4recov

Node 4:
[root@dhcp47-45 ganesha]# ls
dhcp46-219.lab.eng.blr.redhat.com  dhcp47-3.lab.eng.blr.redhat.com   v4old
dhcp46-241.lab.eng.blr.redhat.com  dhcp47-59.lab.eng.blr.redhat.com  v4recov

New Node which is added:
[root@dhcp47-59 ganesha]# ls
dhcp46-219.lab.eng.blr.redhat.com  dhcp47-45.lab.eng.blr.redhat.com  v4old
dhcp46-241.lab.eng.blr.redhat.com  dhcp47-59.lab.eng.blr.redhat.com  v4recov
dhcp47-3.lab.eng.blr.redhat.com    ganesha



Actual results:
ganesha directory and extra hostname directory of the host itself  is created on new node


Expected results:
No ganesha directory and extra hostname directory of the host itself  should be created on new node


Additional info:

Comment 5 Kaleb KEITHLEY 2017-08-21 12:57:05 UTC
storhaug ?