Bug 990408

Summary:	beakerd does not send mail: "TurboMail is not enabled!"
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	scheduler	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	aigao, asaha, dcallagh, llim, qwan, rmancy, xjia
Target Milestone:	0.14	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-09 03:24:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Callaghan 2013-07-31 06:52:57 UTC

Description of problem:
beakerd does not send any mails (in particular, job completion notifications).

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

Steps to Reproduce:
1. Configure mail correctly in /etc/beaker/server.cfg
2. Run beakerd

Actual results:
Notification mails are not sent.
Jul 22 08:05:15 beaker-devel beakerd[12013]: bkr.server.mail WARNING TurboMail is not enabled!

Expected results:
Mails are sent, no warnings about mail being disabled.

Additional info:
Regression in 0.14 due to removal of SIGHUP handling in beakerd. TurboMail's interface.start() is not being called.

Comment 1 Dan Callaghan 2013-07-31 06:56:34 UTC

On Gerrit: http://gerrit.beaker-project.org/2136

Comment 4 Dan Callaghan 2013-08-09 03:24:35 UTC

Beaker 0.14.1 has been released.