Bug 990408 - beakerd does not send mail: "TurboMail is not enabled!"
Summary: beakerd does not send mail: "TurboMail is not enabled!"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.14
Assignee: Dan Callaghan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-31 06:52 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-09 03:24:35 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.