Bug 1330227 - [RFE] The option to turning off the flooding mechanism or configure it is missing
Summary: [RFE] The option to turning off the flooding mechanism or configure it is mis...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.6.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 16:42 UTC by Raz Tamir
Modified: 2017-04-20 07:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-12 08:26:55 UTC
oVirt Team: Infra
Target Upstream Version:


Attachments (Terms of Use)

Description Raz Tamir 2016-04-25 16:42:43 UTC
Description of problem:
In some cases that related to warnings that should be presented to the user, the flooding mechanism will prevent these warning messages to prevent the flooding of the audit log.
The option to configure the flooding mechanism timeout of even disable it is very important for our tests.



Version-Release number of selected component (if applicable):
rhevm-3.6.5.1-0.1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Kaul 2016-04-25 21:03:12 UTC
1. Why is the severity high?
2. Why is it important for tests?
3. It looks like a feature request, why isn't there a keyword for it?

Comment 2 Raz Tamir 2016-04-26 07:25:08 UTC
This bug/RFE was open as a "workaround" to bug 1288862 which caused because the flooding mechanism prevent from the warnings to show up.
We have many case that needs to create large disks (~100GB) and we need this feature of threshold to actually work and shoe the warnings so we will not have to create those large disks.
2nd thing is the threshold feature that is blocked at the moment.

Comment 3 Oved Ourfali 2016-04-27 06:34:23 UTC
I also fail to understand why it is high severity.
Reducing to low.

As for Bug 1288862 we suggested alternatives that were nacked, and the decision by storage team was to close it as wontfix.

Comment 4 Yaniv Kaul 2017-03-12 08:26:55 UTC
(In reply to Oved Ourfali from comment #3)
> I also fail to understand why it is high severity.
> Reducing to low.
> 
> As for Bug 1288862 we suggested alternatives that were nacked, and the
> decision by storage team was to close it as wontfix.

Based on that, and on big changes in logging in VDSM, closing.


Note You need to log in before you can comment on or make changes to this bug.