Description of problem:
The crontab that is created for scap reporting generates an email even when nothing is wrong. This causes a larger issue on big environments. I'd like to see the STDOUT be redirected to /dev/null, and only STDERR generating an email.
Version-Release number of selected component (if applicable):
This is standard behavior. This is a feature change more than a bug report
Steps to Reproduce:
1. install from RPM
2. Schedule a scan
3. verify crontab on remote system
An email is sent containing the STDOUT form the crontab to the root user
The system should only email when there is an issue with the crontab, not during normal processing.
https://github.com/theforeman/puppet-foreman_scap_client/pull/13 covers this change, however it was never implemented. You can modify the /usr/share/puppet/modules/foreman_scap_client/manifests/init.pp file by hand, however any new RPM upgrade will override that change.
Created redmine issue http://projects.theforeman.org/issues/13487 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/13487 has been closed
Merged as https://github.com/theforeman/puppet-foreman_scap_client/commit/3df2fa5e1a79f3b2880ea2ae8b02cfe736e9301a
I do not see this change in /usr/share/puppet/modules/foreman_scap_client/manifests/init.pp
~]# rpm -qav | grep -i puppet-foreman_scap
TESTED with sat62-snap8.1
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.
*** This bug has been marked as a duplicate of bug 1412697 ***