Red Hat Bugzilla – Bug 1236247
[RFE] Email Reporting for OpenSCAP Policy
Last modified: 2016-07-27 05:16:16 EDT
Description of problem: As a user of OpenSCAP in Red Hat Satellite 6.1, I would like the ability to receive email reports (such as those for puppet and errata) for my OpenSCAP Policies. These reports should contain (at a minimum): * Name of the Policy * Listing of hosts whose policy 'status' has changed (i.e, the number of passed/failed/error rules has changed)
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/11085 from this bug
Upstream bug component is SCAP Plugin
Moving to POST since upstream bug http://projects.theforeman.org/issues/11085 has been closed
I have sent the following to Shlomi via email, but so that all information is together, I have pasted it here. ------- In looking at the Email preferences > Notifications section, I note that there is the option "Build a query for audit summary". Does this field operate like the search fields available elsewhere in the Satellite/Foreman web UI? Is there a reference somewhere as to the available query parameters? I'm particularly curious about the following parameters: action, changes, time, user and username. I'll try putting this feature (as I understand it) into a real-life scenario, so that you can either confirm my understanding is correct, or correct my understanding. :D Imagine I have 10 hosts under Satellite management and I have a SCAP policy being run daily on all those hosts. I want to be notified via email if the results of more than 5 rules have changed since the policy was previously run. -------
VERIFIED for satellite-6.2.0-20.1.el6sat.noarch The email reports work fine now.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501