Bug 1400816
| Summary: | [GANESHA] Symlinks from /etc/ganesha/ganesha.conf to shared_storage are created on the non-ganesha nodes in 8 node gluster having 4 node ganesha cluster | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> | |
| Component: | glusterd | Assignee: | Jiffin <jthottan> | |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | low | |||
| Version: | rhgs-3.2 | CC: | aloganat, amukherj, asrivast, bmohanra, jthottan, kkeithle, ndevos, olim, rcyriac, rhinduja, rhs-bugs, skoduri, storage-qa-internal, vbellur | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-25 | Doc Type: | Bug Fix | |
| Doc Text: |
glusterd tries to create symlink "ganesh.conf" on every node of trusted storage pool. Symlink creation fails if the nfs-ganesha package is missing.
Workaround:
Install nfs-ganesha package on all the nodes
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1401877 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-21 04:28:23 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: | 1401877, 1417147 | |||
|
Description
Manisha Saini
2016-12-02 07:23:07 UTC
While trying creating ganesha cluster on 4 nodes out of 8 nodes in gluster,then if any of the node does not have ganesha packages,then it fails to enable nfs-ganesha cluster [root@dhcp47-3 ganesha]# gluster nfs-ganesha enable Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha: failed: Staging failed on dhcp46-232.lab.eng.blr.redhat.com. Error: creation of symlink ganesha.conf in /etc/ganesha failed dhcp46-232.lab.eng.blr.redhat.com -Node which do not have ganesha packages Hitting similar issue, while disabling nfs-ganesha. Steps: 1. Create a storage pool of 4 nodes. 2. Create 4 node nfs-ganesha cluster in the storage pool. 3. Add two new nodes to the storage pool (nfs-ganesha package is not installed on the 2 new nodes) 4. Try to disable 4 node nfs-ganesha cluster. If nfs-ganesha package is not installed on the 2 new nodes, then the user can not disable the existing 4 node nfs-ganesha cluster. [root@dhcp37-145 ~]# gluster nfs-ganesha disable Disabling NFS-Ganesha will tear down entire ganesha cluster across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha: failed: Staging failed on dhcp37-136.lab.eng.blr.redhat.com. Error: removal of symlink ganesha.conf in /etc/ganesha failed Staging failed on dhcp37-115.lab.eng.blr.redhat.com. Error: removal of symlink ganesha.conf in /etc/ganesha failed This has to be documented as a requirement that the nfs-ganesha packages need to be installed on all the nodes of the Gluster trusted storage pool even though only few of them shall be part of nfs-ganesha cluster. Patch got merged upstream : https://review.gluster.org/#/c/16041/ downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101295/ Moving this bug to Assigned state. There were 2 issues reported in this bug. 1.Enabling ganesha on 4 node out of 8 node gluster cluster should not create symlinks to shared-storage on non-ganesha nodes 2.Disabling the 4 node ganesha cluster out of 8 node gluster cluster. Case 1 is fixed and working as expected. Case 2 is still failing for nodes which do not have ganesha packages. While disabling 4 node ganesha cluster on 8 node gluster cluster # gluster nfs-ganesha disable Disabling NFS-Ganesha will tear down entire ganesha cluster across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha: failed: Staging failed on dhcp46-56.lab.eng.blr.redhat.com. Error: removal of symlink ganesha.conf in /etc/ganesha failed Staging failed on dhcp46-109.lab.eng.blr.redhat.com. Error: removal of symlink ganesha.conf in /etc/ganesha failed Out of the other 4 node on which ganesha cluster is not there, 2 node does not have ganesha packages.So while disabling ganesha,its throwing staging failed messages for those node not having ganesha packages. (In reply to Manisha Saini from comment #11) > Moving this bug to Assigned state. > > There were 2 issues reported in this bug. > > 1.Enabling ganesha on 4 node out of 8 node gluster cluster should not create > symlinks to shared-storage on non-ganesha nodes > > 2.Disabling the 4 node ganesha cluster out of 8 node gluster cluster. > > > Case 1 is fixed and working as expected. > Case 2 is still failing for nodes which do not have ganesha packages. > > > While disabling 4 node ganesha cluster on 8 node gluster cluster > > # gluster nfs-ganesha disable > Disabling NFS-Ganesha will tear down entire ganesha cluster across the > trusted pool. Do you still want to continue? > (y/n) y > This will take a few minutes to complete. Please wait .. > nfs-ganesha: failed: Staging failed on dhcp46-56.lab.eng.blr.redhat.com. > Error: removal of symlink ganesha.conf in /etc/ganesha failed > Staging failed on dhcp46-109.lab.eng.blr.redhat.com. Error: removal of > symlink ganesha.conf in /etc/ganesha failed > > > > Out of the other 4 node on which ganesha cluster is not there, 2 node does > not have ganesha packages.So while disabling ganesha,its throwing staging > failed messages for those node not having ganesha packages. Patch posted upstream to fix this issue https://review.gluster.org/#/c/17138/ Downstream patch link https://code.engineering.redhat.com/gerrit/#/c/105741/ Verified this bug on # rpm -qa | grep ganesha glusterfs-ganesha-3.8.4-26.el7rhgs.x86_64 nfs-ganesha-2.4.4-6.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.4-6.el7rhgs.x86_64 Enabling and disabling 4 node ganesha cluster on 8 node gluster cluster is successfull even when the ganesha packages are not present on non-ganesha nodes. Moving this bug to verified state. 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://access.redhat.com/errata/RHBA-2017:2774 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://access.redhat.com/errata/RHBA-2017:2774 |