Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
All

How reproducible:
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

Actual results:
An email is sent containing the STDOUT form the crontab to the root user

Expected results:
The system should only email when there is an issue with the crontab, not during normal processing.

Additional info:
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
-------------
Shlomi Zadok
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
puppet-foreman_scap_client-0.3.3-10.el7sat.noarch


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.

https://access.redhat.com/errata/RHBA-2016:1501

*** This bug has been marked as a duplicate of bug 1412697 ***