Description of problem: Libgfapi-python functions discard and fallocate fails with "AttributeError: /lib64/libgfapi.so.0: undefined symbol: glfs_discard", when defined with ctype function prototypes. glfs_discard = ctypes.CFUNCTYPE(ctypes.c_int, ctypes.c_void_p, ctypes.c_ulong, ctypes.c_size_t)((' glfs_discard', client)) glfs_fallocate = ctypes.CFUNCTYPE(ctypes.c_int, ctypes.c_void_p, ctypes.c_int, ctypes.c_ulong, ctypes.c_size_t) (('glfs_fallocate', client)) Version-Release number of selected component (if applicable): http://review.gluster.org/#/c/7805/ How reproducible: Run functional tests inside "tests" directory in the source after defining the function prototypes. Actual results: It fails to pass functional tests. Expected results: It should work when function prototypes are defined as shown in http://review.gluster.org/#/c/7805/
I'm not sure this is still an issue? $ objdump -T /usr/lib64/libgfapi.so.0 | grep -e discard -e fallocate 0000000000000000 DF *UND* 0000000000000000 syncop_fallocate 0000000000000000 DF *UND* 0000000000000000 syncop_discard 000000000000d710 g DF .text 00000000000000da Base glfs_discard_async 000000000000f440 g DF .text 00000000000000d5 Base glfs_fallocate 000000000000f520 g DF .text 00000000000000bd Base glfs_discard $ rpm -q glusterfs-api glusterfs-api-3.5.20141021.946eecf-1.fc20.x86_64 http://review.gluster.org/#/c/7805/ is for the external libgfapi-python repository, not for the bundled version that the glusterfs sources include. Should this bug be assigned to libgfapi-python component? And, should we maybe start a discussion about removing the python bits from the glusterfs repository and use the dedicated libgfapi-python repository?
If this is still an issue, please re-open this bug report.
This bug has been CLOSED, and there has not been a response to the requested NEEDINFO in more than 4 weeks. The NEEDINFO flag is now getting cleared so that our Bugzilla household is getting more in order.