Bug 1486542

Summary:	"ganesha.so cannot open" warning message in glusterd log in non ganesha setup.
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	glusterd	Assignee:	Jiffin <jthottan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	3.10	CC:	amukherj, bsrirama, bugs, jthottan, kramdoss, ndevos, rhs-bugs, rnalakka, sasundar, sbhaloth, skoduri, srangana, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.10.11	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1378371	Environment:
Last Closed:	2018-03-10 12:37:56 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:	1480863

Description Jiffin 2017-08-30 05:22:02 UTC

+++ This bug was initially created as a clone of Bug #1378371 +++

Description of problem:
=======================
I am seeing below warning message in glusterd log after node reboot.


[2016-09-22 09:38:33.987943] I [MSGID: 106502] [glusterd-handler.c:2831:__glusterd_handle_friend_update] 0-management: Received my uuid as Friend
[2016-09-22 09:39:37.453790] W [MSGID: 101095] [xlator.c:147:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.8.4/xlator/features/ganesha.so: cannot open shared object file: No such file or directory

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.8.4-1


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Have 3.1.3 setup with simple distribute/replica volume and update it to 3.2 
2. reboot the node
3. Check the glusterd log for the ganesha.so warning message 

Actual results:
===============
Getting "ganesha.so  cannot open shared object file: No such file or directory" warning message in glusterd log after node reboot in non ganesha setup.


Expected results:
==================
This warning should not throw after node reboot.

Additional info:

RCA : 
I have never reproduced this issue in my setup. So following is my assumption.
ganesha.so file is created because of client side ganesha xlator, in 3.10 code base there are some files related to ganesha xlator.

# ls xlators/features/ganesha/
Makefile  Makefile.in  src

Comment 1 Worker Ant 2017-08-30 05:49:10 UTC

REVIEW: https://review.gluster.org/18147 (xlators/ganesha : remove ganesha xlator code from 3.10) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)

Comment 2 Worker Ant 2017-09-07 11:43:16 UTC

COMMIT: https://review.gluster.org/18147 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) 
------
commit 8416e31b23cf6c7a6272d4779026eca2f5b63fe8
Author: Jiffin Tony Thottan <jthottan>
Date:   Wed Aug 30 10:54:24 2017 +0530

    xlators/ganesha : remove ganesha xlator code from 3.10
    
    The commit e4a4043 have removed ganesha xlator from glusterfs codebase.
    But while reverting back ganesha changes, the Makefile.am in xlators/ganesha
    got resurrected.
    
    Change-Id: I6efaacaf1fe426da974608ddac5eae4a43800983
    BUG: 1486542
    Signed-off-by: Jiffin Tony Thottan <jthottan>
    Reviewed-on: https://review.gluster.org/18147
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: soumya k <skoduri>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 3 Shyamsundar 2017-10-06 17:10:52 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.6, please open a new bug report.

glusterfs-3.10.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-October/000084.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 4 Worker Ant 2018-02-27 10:11:47 UTC

REVIEW: https://review.gluster.org/19639 (glusterd/ganesha : change voltype for ganesha.enable in volume option table) posted (#1) for review on release-3.10 by jiffin tony Thottan

Comment 5 Worker Ant 2018-03-01 02:03:43 UTC

COMMIT: https://review.gluster.org/19639 committed in release-3.10 by "jiffin tony Thottan" <jthottan> with a commit message- glusterd/ganesha : change voltype for ganesha.enable in volume option table

The voltype defined for ganesha.enable is features/ganesha. But ganesha xlator
was removed from client stack long back. Now it is defined as part of glusterd.
So reflecting the same on the volume option table.

Change-Id: Ifedd7493020b77bd54edfdbdd9c799d93b24d0aa
BUG: 1486542
Signed-off-by: Jiffin Tony Thottan <jthottan>

Comment 6 Shyamsundar 2018-03-10 12:37:56 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.11, please open a new bug report.

glusterfs-3.10.11 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-March/000091.html
[2] https://www.gluster.org/pipermail/gluster-users/