Description of problem: Some emails from Beaker are sent with notification headers and some not. Version-Release number of selected component (if applicable): 0.12 How reproducible: Steps to Reproduce: 1. Check all the emails generated by 'beaker' 2. 3. Actual results: Some do have beaker specific headers, some do not. Expected results: All behave consistently Additional info:
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: X-Beaker-Notification X-Beaker-System X-Lender X-Owner X-Location X-Lab-Controller X-Vendor X-Type X-Arch Job completion notifications include: X-Beaker-Notification X-Beaker-Job-ID Group membership notifications include: X-Beaker-Notification X-Beaker-Group X-Beaker-Group-Action 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.