Bug 1324673

Summary:	Include hostname in ovirt-ha-agent emails
Product:	[oVirt] ovirt-hosted-engine-ha	Reporter:	Avi Miller <avi.miller>
Component:	Agent	Assignee:	Shira Maximov <mshira>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.3.5.1	CC:	bugs, dfediuck, fdeutsch, gklein, mavital, melewis, mgoldboi, mshira, rgolan
Target Milestone:	ovirt-4.0.0-rc	Keywords:	Improvement, Triaged
Target Release:	2.0.0	Flags:	rule-engine: ovirt-4.0.0+ gklein: testing_plan_complete- mgoldboi: planning_ack+ dfediuck: devel_ack+ mavital: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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}.'	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-05 07:59:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.