Bug 1032644 - hosted engine email notifications cause email flood.
Summary: hosted engine email notifications cause email flood.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-ha
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Martin Sivák
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 14:15 UTC by Leonid Natapov
Modified: 2016-02-10 20:16 UTC (History)
6 users (show)

Fixed In Version: ovirt-hosted-engine-ha-0.1.0-0.8.rc.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:51:25 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0080 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-ha 2014-01-21 21:00:07 UTC
oVirt gerrit 21466 0 None None None Never

Description Leonid Natapov 2013-11-20 14:15:12 UTC 
There is a loop that we use to compute the state transitions that is properly handled by the code but in the case we need to collect external data, we leave the function, do our stuff and re-execute the handling loop and that means we send another email. So on each log we send an email which means email each 10 seconds.
Comment 1 Greg Padgett 2013-11-21 20:45:44 UTC 
Merged Change-Id: I4f35d85472f9e27bad222254a4d5c81b845d6282
Comment 3 Artyom 2013-12-08 09:14:54 UTC 
Verified on ovirt-hosted-engine-ha-0.1.0-0.8.rc.el6ev.noarch
Comment 4 errata-xmlrpc 2014-01-21 16:51:25 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.

http://rhn.redhat.com/errata/RHEA-2014-0080.html
Note You need to log in before you can comment on or make changes to this bug.