Bug 1545724

Summary:	libgfrpc does not export IPv6 RPC methods even with --with-ipv6-default
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	rpc	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	high
Version:	4.0	CC:	atumball, bugs, rgowdapp, sheenobu+redhat
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1544961	Environment:
Last Closed:	2018-03-15 11:27:04 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:	1544961
Bug Blocks:	1539842

Description Kaleb KEITHLEY 2018-02-15 14:33:30 UTC

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

Description of problem:

Methods rpcsvc_program_register_rpcbind6/rpcsvc_program_unregister_rpcbind6 do not get exported with the symbol table when compiling --with-ipv6-default.

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

4.0, mainline

How reproducible:

Always

Steps to Reproduce:
1. Compile gluster with --with-ipv6-default. 
2. Check exported symbols of libgfrpc.so, see no rpcbind6

1. Compile gluster with --with-ipv6-default, --with-gnfs 
2. Run gluster
3. See nfs daemon crash with unable to lookup symbol rpcsvc_program_register_rpcbind6

Actual results:

libgfrpc does not have rpcbind6. gnfsd crashes with symbol import error.

nm -D /usr/lib64/libgfrpc.so -l | grep rpcbind6; echo $? => 1

nfs.log:

[2018-02-13 21:08:27.351949] W [MSGID: 101095] [xlator.c:433:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.8dev/xlator/nfs/server.so: undefined symbol: rpcsvc_program_register_rpcbind6


Expected results:

libgfrpc has rpcbind6. gnfsd runs and listens ipv6 address.

nm -D /usr/lib64/libgfrpc.so -l | grep rpcbind6; echo $? => 0

Additional info:

Bug introduced when file rpc-lib/src/libgfrpc.sym was introduced. fix simple, incoming.

--- Additional comment from Worker Ant on 2018-02-13 18:05:52 EST ---

REVIEW: https://review.gluster.org/19563 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#1) for review on master by

--- Additional comment from Worker Ant on 2018-02-14 10:48:08 EST ---

COMMIT: https://review.gluster.org/19563 committed in master by  with a commit message- rpc: Adds rpcbind6 programs to libgfrpc symbols

Building with --with-default-ipv6 causes shared
components of gluster calling the rpcbind6 functions
to fail. Adding the symbols in the list is all that is
necessary. Building without ipv6 keeps the same behavior.

No test cases as this is a build-specific fix.

Change-Id: I248d3291bf17326b07d152d9b79cdcfaf9068f0d
BUG: 1544961
Signed-off-by: Sheena Artrip <sheenobu>

--- Additional comment from Worker Ant on 2018-02-15 09:20:24 EST ---

REVIEW: https://review.gluster.org/19573 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#1) for review on release-4.0 by Kaleb KEITHLEY

Comment 1 Worker Ant 2018-02-15 14:34:56 UTC

REVIEW: https://review.gluster.org/19573 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#2) for review on release-4.0 by Kaleb KEITHLEY

Comment 2 Worker Ant 2018-02-18 03:32:28 UTC

COMMIT: https://review.gluster.org/19573 committed in release-4.0 by "Kaleb KEITHLEY" <kkeithle> with a commit message- rpc: Adds rpcbind6 programs to libgfrpc symbols

Building with --with-default-ipv6 causes shared
components of gluster calling the rpcbind6 functions
to fail. Adding the symbols in the list is all that is
necessary. Building without ipv6 keeps the same behavior.

No test cases as this is a build-specific fix.

Change-Id: I248d3291bf17326b07d152d9b79cdcfaf9068f0d
BUG: 1545724
Signed-off-by: Sheena Artrip <sheenobu>

Comment 3 Shyamsundar 2018-03-15 11:27:04 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-4.0.0, please open a new bug report.

glusterfs-4.0.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/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/