[Bugs] [Bug 1387964] New: [Eventing]: 'gluster vol bitrot <volname> scrub ondemand' does not produce an event
bugzilla at redhat.com
bugzilla at redhat.com
Mon Oct 24 05:05:42 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1387964
Bug ID: 1387964
Summary: [Eventing]: 'gluster vol bitrot <volname> scrub
ondemand' does not produce an event
Product: GlusterFS
Version: 3.9
Component: bitrot
Severity: medium
Assignee: bugs at gluster.org
Reporter: khiremat at redhat.com
CC: amukherj at redhat.com, bugs at gluster.org,
sanandpa at redhat.com, storage-qa-internal at redhat.com,
vbellur at redhat.com
Depends On: 1384311, 1387864
Docs Contact: bugs at gluster.org
+++ This bug was initially created as a clone of Bug #1387864 +++
+++ This bug was initially created as a clone of Bug #1384311 +++
Description of problem:
========================
When we pause/resume the bitrot scrubber, it generates an event
BITROT_SCRUB_OPTION, as there is a change in the scrub option. Similarly when
we change the frequency to hourly/daily/weekly, it again generates an event
BITROT_SCRUB_FREQ, as there is a change in the scrub frequency. Likewise, if we
trigger the scrubber on demand, it necessitates a change in the system, thus
producing an event. However, no event is generated/seen when the scrubber is
triggered ondemand.
Version-Release number of selected component (if applicable):
============================================================
How reproducible:
=================
Always
Steps to Reproduce:
====================
1. Have a 4 node cluster, with a plain distribute volume. Enable eventing, and
register a webhook, as a listener.
2. Create a volume 'vol1' and start it. The corresponding events are seen, as
expected
3. Enable bitrot, change the scrub frequency and also try to pause/resume.
Watch out for the related events BITROT_ENABLE, BITROT_SCRUB_FREQ,
BITROT_SCRUB_OPTION.
4. Trigger the scrubber on demand, and monitor if the event BITROT_SCRUB_OPTION
is seen
Actual results:
==============
All expected events seen from step1 to 3. No event seen at step4
Expected results:
================
An event is expected at step4
--- Additional comment from Worker Ant on 2016-10-22 14:30:42 EDT ---
REVIEW: http://review.gluster.org/15700 (bitrot/cli: Add ondemand scrub event)
posted (#1) for review on master by Kotresh HR (khiremat at redhat.com)
--- Additional comment from Worker Ant on 2016-10-23 02:39:46 EDT ---
COMMIT: http://review.gluster.org/15700 committed in master by Atin Mukherjee
(amukherj at redhat.com)
------
commit 255cc64375abe2925c7da1e13e45018dad4462df
Author: Kotresh HR <khiremat at redhat.com>
Date: Sat Oct 22 23:50:02 2016 +0530
bitrot/cli: Add ondemand scrub event
Following Bitrot Events are added
BITROT_SCRUB_ONDEMAND
{
"nodeid": NODEID,
"ts": TIMESTAMP,
"event": EVENT_TYPE,
"message": {
"name": VOLUME_NAME,
}
}
Change-Id: I85e668e254e6f29c447ddb4ad2ce2fc04f98bf3c
BUG: 1387864
Signed-off-by: Kotresh HR <khiremat at redhat.com>
Reviewed-on: http://review.gluster.org/15700
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1384311
[Bug 1384311] [Eventing]: 'gluster vol bitrot <volname> scrub ondemand'
does not produce an event
https://bugzilla.redhat.com/show_bug.cgi?id=1387864
[Bug 1387864] [Eventing]: 'gluster vol bitrot <volname> scrub ondemand'
does not produce an event
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.
More information about the Bugs
mailing list