Bug 1352423

Summary:	should find_library("c") be used instead of find_library("libc") in geo-replication/syncdaemon/libcxattr.py?
Product:	[Community] GlusterFS	Reporter:	Saravanakumar <sarumuga>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	avishwan, bugs, smohan, tereshonkov.roman
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1318296	Environment:
Last Closed:	2017-03-27 18:21:34 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:	1318296
Bug Blocks:

Description Saravanakumar 2016-07-04 06:59:52 UTC

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

Description of problem:

In geo-replication/syncdaemon/libcxattr.py
is it right to use 
libc = CDLL(find_library("libc"))
instead of 
libc = CDLL(find_library("c"))


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-07-04 07:04:41 UTC

REVIEW: http://review.gluster.org/14852 (geo-rep: fix wrong argument to find_library) posted (#1) for review on master by Saravanakumar Arumugam (sarumuga)

Comment 2 Vijay Bellur 2016-07-07 10:50:00 UTC

COMMIT: http://review.gluster.org/14852 committed in master by Aravinda VK (avishwan) 
------
commit 3b61a00f0afc7f84e7685548cbcde3b69172adf0
Author: Saravanakumar Arumugam <sarumuga>
Date:   Mon Jul 4 12:21:45 2016 +0530

    geo-rep: fix wrong argument to find_library
    
    Argument passed to find_library function is wrong.
    Pass proper argument to find_library.
    
    Note: It still works as default handle is libc.
    
    Change-Id: I4657a3ef9f5249e3eec4a20582856b58168126ce
    BUG: 1352423
    Signed-off-by: Saravanakumar Arumugam <sarumuga>
    Reviewed-on: http://review.gluster.org/14852
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>

Comment 3 Shyamsundar 2017-03-27 18:21:34 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.9.0, please open a new bug report.

glusterfs-3.9.0 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/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/