[Bugs] [Bug 1387964] [Eventing]: 'gluster vol bitrot <volname> scrub ondemand' does not produce an event

bugzilla at redhat.com bugzilla at redhat.com
Mon Oct 24 05:06:26 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1387964

Kotresh HR <khiremat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |khiremat at redhat.com



--- Comment #1 from Kotresh HR <khiremat at redhat.com> ---
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

-- 
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