Bug 1361983

Summary:	Move USE_EVENTS in gf_events API
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	eventsapi	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	avishwan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-27 18:21: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:
Bug Blocks:	1351589

Description Atin Mukherjee 2016-08-01 06:29:55 UTC

Description of problem:

Having conditional macro USE_EVENTS inside gf_events API will ease consumers to just use the API directly instead of using the condition every time.

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-08-01 06:30:35 UTC

REVIEW: http://review.gluster.org/15054 (events: move conditional macro check USE_EVENTS inside gf_events) posted (#1) for review on master by Atin Mukherjee (amukherj)

Comment 2 Vijay Bellur 2016-08-02 11:13:18 UTC

COMMIT: http://review.gluster.org/15054 committed in master by Aravinda VK (avishwan) 
------
commit 8e797e6f4b95d759d5a2d6c072401c9eb5fcf68e
Author: Atin Mukherjee <amukherj>
Date:   Mon Aug 1 11:56:27 2016 +0530

    events: move conditional macro check USE_EVENTS inside gf_events
    
    Change-Id: I88279b11b648e676a4544bbb55c7466fbc55ffa7
    BUG: 1361983
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/15054
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Aravinda VK <avishwan>

Comment 3 Shyamsundar 2017-03-27 18:21: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-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/