Bug 1324673 - Include hostname in ovirt-ha-agent emails
Summary: Include hostname in ovirt-ha-agent emails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-ha
Classification: oVirt
Component: Agent
Version: 1.3.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-rc
: 2.0.0
Assignee: Shira Maximov
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 22:54 UTC by Avi Miller
Modified: 2016-07-08 01:49 UTC (History)
9 users (show)

Fixed In Version: ovirt-hosted-engine-ha-2.0.0
Doc Type: Enhancement
Doc Text:
With this update, the self-hosted engine hostname is now included in ovirt-ha-agent emails. This means that the emails are now clearer. An example of the generated email content is 'Hosted engine host: {hostname} changed state: {detail}.'
Clone Of:
Environment:
Last Closed: 2016-07-05 07:59:36 UTC
oVirt Team: SLA
rule-engine: ovirt-4.0.0+
gklein: testing_plan_complete-
mgoldboi: planning_ack+
dfediuck: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 57495 0 master MERGED Add hostname in ovirt-ha-agent emails 2016-05-26 14:58:05 UTC

Description Avi Miller 2016-04-06 22:54:45 UTC 
Description of problem:

Currently, all the emails sent by all nodes that are capable of running the Hosted Engine VM all send identical emails. This makes it difficult to determine which host is experiencing issues.

Version-Release number of selected component (if applicable):

ovirt-hosted-engine-ha-1.3.5.1-1


How reproducible:

100%


Steps to Reproduce:
1. Setup a multi-node oVirt Hosted Engine Setup
2. Setup email delivery
3. Review content of email text received from each node

Actual results:
All emails are identical making host identification difficult (can see the source host in the raw headers, but this is tedious).

Expected results:
Emails should include the name of the host so that they can be easily identified.


Additional info:
Comment 1 Yaniv Kaul 2016-04-25 12:08:48 UTC 
Roy:
1. Is this an improvement? If it is, need 'FutureFeature' flag.
2. Is Shira going to handle this?
Comment 3 Roy Golan 2016-05-01 09:06:20 UTC 
(In reply to Yaniv Kaul from comment #1)
> Roy:
> 1. Is this an improvement? If it is, need 'FutureFeature' flag.
> 2. Is Shira going to handle this?

I'll set the keyword. And yes, since this kind of fixes are perfect for contribution Shira gladly accepted that.
Comment 4 Sandro Bonazzola 2016-05-02 10:05:48 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 5 Yaniv Lavi 2016-05-23 13:20:18 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 6 Yaniv Lavi 2016-05-23 13:23:46 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 7 Artyom 2016-06-05 13:27:03 UTC 
Verified on ovirt-hosted-engine-ha-2.0.0-1.el7ev.noarch
Comment 8 Sandro Bonazzola 2016-07-05 07:59:36 UTC 
oVirt 4.0.0 has been released, closing current release.
Note You need to log in before you can comment on or make changes to this bug.