Red Hat Bugzilla – Bug 965341
Update emails to add Beaker specific headers
Last modified: 2018-02-05 19:41:31 EST
Description of problem:
Some emails from Beaker are sent with notification headers and some not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Check all the emails generated by 'beaker'
Some do have beaker specific headers, some do not.
All behave consistently
Beaker's notification mails all include at least an X-Beaker-Notification header, indicating the type of notification, as well as further X- headers giving extra metadata about the notification. System loan requests, problem reports, and broken notifications include the following headers:
Job completion notifications include:
Group membership notifications include:
If there are any further requests for more headers not already covered, they can be filed as new RFEs.
The reservation email is sent directly by the reservesys task rather than by the server. If that's what this BZ was alluding to, it may be addressed by the RFE to add a server based scheduled reservation mechanism.