Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1447116

Summary: gfapi exports non-existing glfs_upcall_inode_get_event symbol
Product: [Community] GlusterFS Reporter: Niels de Vos <ndevos>
Component: libgfapiAssignee: Niels de Vos <ndevos>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.12.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-05 17:27:45 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:

Description Niels de Vos 2017-05-01 19:24:49 UTC
Description of problem:
The function is glfs_upcall_get_event() instead.

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

Comment 1 Worker Ant 2017-05-01 19:25:29 UTC
REVIEW: https://review.gluster.org/17135 (api: fix typo of glfs_upcall_get_event) posted (#2) for review on master by Kinglong Mee

Comment 2 Worker Ant 2017-05-02 12:45:43 UTC
COMMIT: https://review.gluster.org/17135 committed in master by Niels de Vos (ndevos) 
------
commit 8b4e7cb692f1f6e7612bc2c4565e2a834e530a3a
Author: Kinglong Mee <mijinlong>
Date:   Fri Apr 28 05:45:16 2017 -0400

    api: fix typo of glfs_upcall_get_event
    
    glfs_upcall_inode_get_event is not exist.
    
    Change-Id: I27bd7eb9bf99d3289ae12fe31405d3b46855152d
    BUG: 1447116
    Signed-off-by: Kinglong Mee <mijinlong>
    Reviewed-on: https://review.gluster.org/17135
    Reviewed-by: Niels de Vos <ndevos>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-09-05 17:27:45 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.12.0, please open a new bug report.

glusterfs-3.12.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/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/