[Bugs] [Bug 1375914] New: posix: Integrate important events with events framework
bugzilla at redhat.com
bugzilla at redhat.com
Wed Sep 14 08:47:53 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1375914
Bug ID: 1375914
Summary: posix: Integrate important events with events
framework
Product: GlusterFS
Version: 3.9
Component: posix
Assignee: bugs at gluster.org
Reporter: pkarampu at redhat.com
CC: bugs at gluster.org
Depends On: 1371353
Blocks: 1361086
+++ This bug was initially created as a clone of Bug #1371353 +++
Description of problem:
Integrate important events from posix xlator with events framework.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Worker Ant on 2016-08-29 22:01:08 EDT ---
REVIEW: http://review.gluster.org/15342 (storage/posix: Integrate important
events with gf_event) posted (#1) for review on master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
--- Additional comment from Worker Ant on 2016-08-29 22:28:19 EDT ---
REVIEW: http://review.gluster.org/15342 (storage/posix: Integrate important
events with gf_event) posted (#2) for review on master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
--- Additional comment from Worker Ant on 2016-09-13 19:16:17 EDT ---
REVIEW: http://review.gluster.org/15342 (storage/posix: Integrate important
events with gf_event) posted (#3) for review on master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
--- Additional comment from Worker Ant on 2016-09-14 04:27:22 EDT ---
REVIEW: http://review.gluster.org/15342 (storage/posix: Integrate important
events with gf_event) posted (#4) for review on master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1361086
[Bug 1361086] [RFE]: posix events
https://bugzilla.redhat.com/show_bug.cgi?id=1371353
[Bug 1371353] posix: Integrate important events with events framework
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list