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):
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
libgfrpc does not have rpcbind6. gnfsd crashes with symbol import error.
nm -D /usr/lib64/libgfrpc.so -l | grep rpcbind6; echo $? => 1
[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
libgfrpc has rpcbind6. gnfsd runs and listens ipv6 address.
nm -D /usr/lib64/libgfrpc.so -l | grep rpcbind6; echo $? => 0
Bug introduced when file rpc-lib/src/libgfrpc.sym was introduced. fix simple, incoming.
REVIEW: https://review.gluster.org/19563 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#1) for review on master by
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.
Signed-off-by: Sheena Artrip <email@example.com>
REVIEW: https://review.gluster.org/19573 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#1) for review on release-4.0 by Kaleb KEITHLEY
REVISION POSTED: https://review.gluster.org/19573 (rpc: Adds rpcbind6 programs to libgfrpc symbols) posted (#2) for review on release-4.0 by Kaleb KEITHLEY
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-v4.1.0, please open a new bug report.
glusterfs-v4.1.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.