Bug 1013631 - No email notification sent when host recovers from previously reported condition
No email notification sent when host recovers from previously reported condition
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-notification-service (Show other bugs)
3.2.0
All Linux
medium Severity medium
: ---
: 3.4.0
Assigned To: Ravi Nori
Tareq Alayan
infra
:
Depends On:
Blocks: 643924 rhev3.4beta 1142926
  Show dependency treegraph
 
Reported: 2013-09-30 09:25 EDT by Julio Entrena Perez
Modified: 2016-02-10 14:01 EST (History)
11 users (show)

See Also:
Fixed In Version: ovirt-3.4.0-beta3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-12 10:03:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
scrnshot (163.03 KB, image/png)
2014-02-17 11:11 EST, Tareq Alayan
no flags Details
notifier log (4.57 KB, application/x-tar-gz)
2014-02-20 09:09 EST, Tareq Alayan
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1228453 None None None Never
oVirt gerrit 23399 None None None Never
oVirt gerrit 24170 None None None Never
oVirt gerrit 24848 None None None Never
oVirt gerrit 24955 None None None Never

  None (edit)
Description Julio Entrena Perez 2013-09-30 09:25:20 EDT
Description of problem:
Users can choose to receive email notifications for several host conditions listed under "Host Event" section of event notifications.

When a user has chosen a specific condition and such condition occurs the user receives an email notification.

When such condition is resolved or disappears the user does not receive any email notification alerting him/her that the previously reported condition has been solved is no longer present.

Version-Release number of selected component (if applicable):
rhevm-notification-service-3.2.2-0.41.el6ev.

How reproducible:
Always.

Steps to Reproduce:
1. In webadmin portal go to "Users" resource tab and choose a user from the list.
2. Choose the "Event Notifier" sub-tab and click the "Manage Events" button.
3. Expand "Host Events" to show all host related notifications available.

Actual results:
There is no option to receive an email notification when a previously reported condition is fixed, e.g. when a non-operational host comes back.

Expected results:
An option like "Host state was set back to Operational/Up" is available.
Selecting this option causes event notification email to be sent when a previously reported condition is fixed.


Additional info:
Comment 3 Ravi Nori 2014-01-17 12:05:44 EST
I have pushed a patch to add a new event that the user can subscribe to "Host is responsive".
Comment 5 Arthur Berezin 2014-02-02 11:02:41 EST
Barak, can you ack for 3.4?
Comment 6 Tareq Alayan 2014-02-17 08:30:27 EST
is this merged into upstream?
Comment 7 Eli Mesika 2014-02-17 10:11:11 EST
Tareq , you can see that in the External Trackers section above 
Yes it was merged
Comment 8 Tareq Alayan 2014-02-17 11:11:33 EST
Created attachment 864163 [details]
scrnshot

there is no event "Host is responsive" user can subscribe to

see screen shot 


tested on ovirt-engine-tools-3.4.0-0.7.beta2.el6.noarch
Comment 9 Ravi Nori 2014-02-17 12:12:17 EST
The patch does not add a new notifcation for the user to subscribe to. 

If the user is subscribed to "Host state was set to non operation" or "Host is non responsive". The user should get a email notification when a host ges into non-responsive or non-operational status. Now if the host changes state to UP/Maintenance the user should get a second email notification indicating that the previously reported condition has been resolved.

This requires that the notification service has been configured with the smtp mail server address and is running.

Please retest it
Comment 10 Tareq Alayan 2014-02-17 12:27:34 EST
Thanks Ravi, 

I subscribed to to Host non responsive event, and i got email about the non responsive state and then email about host going up again Issue Solved Notification. (vm-161-144.scl.lab.tlv.redhat.com), [Host rose04 was activated by admin.]

tested on ovirt-engine-tools-3.4.0-0.7.beta2.el6.noarch
Comment 11 Sandro Bonazzola 2014-02-19 07:26:32 EST
This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA
Comment 12 Tareq Alayan 2014-02-20 09:08:38 EST
I subscribed to to Host non responsive event, and i got email about the non responsive state, but i did not got email that the issue have been resolved. 

tested on 
ovirt-engine-3.4.0-0.11.beta3.el6.noarch
ovirt-engine-tools-3.4.0-0.11.beta3.el6.noarch
Comment 13 Tareq Alayan 2014-02-20 09:09:41 EST
Created attachment 865538 [details]
notifier log
Comment 14 Eli Mesika 2014-02-20 09:12:46 EST
(In reply to Tareq Alayan from comment #12)
> I subscribed to to Host non responsive event, and i got email about the non
> responsive state, but i did not got email that the issue have been resolved. 
> 
> tested on 
> ovirt-engine-3.4.0-0.11.beta3.el6.noarch
> ovirt-engine-tools-3.4.0-0.11.beta3.el6.noarch

Please provide full details on how you had tested , how the host became non-responsive and what do you did in order to make it responsive again
Comment 15 Tareq Alayan 2014-02-20 09:24:46 EST
I stopped the vdsmd process.
It became Connecting the Non responsive and the UP (soft fencing recovering)   
Got email that About becoming non responsive and no email regarding the host set to UP.
Comment 16 Tareq Alayan 2014-03-12 08:52:49 EDT
is this merged into rhevm-tools-3.4.0-0.3.master.el6ev.noarch
Comment 17 Ravi Nori 2014-03-12 09:02:08 EDT
Yes, the patch has been merged into ovirt-engine 3.4
Comment 18 Tareq Alayan 2014-03-18 08:17:52 EDT
verified on rhevm-tools-3.4.0-0.5.master.el6ev.noarch
resolution mail has been received.
Comment 19 Itamar Heim 2014-06-12 10:03:43 EDT
Closing as part of 3.4.0

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