Bug 1360807

Summary: [RFE] Generate events in GlusterD
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Atin Mukherjee <amukherj>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Byreddy <bsrirama>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone: ---Keywords: FutureFeature
Target Release: RHGS 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: USM-Gluster integration
Fixed In Version: glusterfs-3.8.4-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1360809 (view as bug list) Environment:
Last Closed: 2017-03-23 05:40:29 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: 1351503, 1360809    

Description Atin Mukherjee 2016-07-27 14:15:48 UTC
Description of problem:

This RFE is to track the changes required in the glusterd component to capture all the async events which are required for eventing framework to consume them.

Comment 2 Atin Mukherjee 2016-08-09 05:04:55 UTC
Upstream patch http://review.gluster.org/15015 posted for review. There would be one more patch to cover the rest of the events from GlusterD.

Comment 4 Atin Mukherjee 2016-08-23 14:02:29 UTC
http://review.gluster.org/#/c/15153/ is the other patch posted for review.

Comment 5 Atin Mukherjee 2016-09-16 10:48:15 UTC
Following downstream patches are merged now:

https://code.engineering.redhat.com/gerrit/#/c/84793/
https://code.engineering.redhat.com/gerrit/#/c/84795/

Comment 10 Byreddy 2016-11-03 08:48:52 UTC
Verified this RFE using the build 3.8.4-3.

events are generated when cluster and volume operations happened in the backend.

Moving to verified state.

Comment 12 errata-xmlrpc 2017-03-23 05:40:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0486.html