Assigning to Sergei for review.
I agree - I don't think it makes sense to add this note to the documentation, as it tells customers that they can ignore a warning they generate by doing something that we don't just not tell them how to do, but tell them (in the comments of the cron job) that they shouldn't do.
I'm guessing that customers learn how to run the command manually by looking into the cron job, so I suggest that we put the warning there, along the lines of:
$ crontab -l
# HEADER: This file was autogenerated at 2017-01-09 07:56:17 +0000 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Manually executing foreman_scap_client manually will generate errors
due to reference to missing files.
# HEADER: If you have run foreman_scap_client manually you can safely ignore errors due to missing http://www.redhat.com/security/data/oval/Red_Hat_Enterprise_Linux_7.xml.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: foreman_scap_client_1
0 1 * * 1 /usr/bin/foreman_scap_client 1
Thank you Steve for comment 6
I see only one Sat6 scap component in bugzilla. Reassigning this bug to "Scap Plugin" as I do not know who owns the foreman_scap_client script.
Created redmine issue http://projects.theforeman.org/issues/21389 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21389 has been resolved.
build :Satellite 6.4.0 snap21
Unable find the warning, maybe it missed the snap
Build: Satellite 6.5.0 snap8
The scap cron file has the required warning
# DO NOT EDIT THIS FILE MANUALLY
# IT IS MANAGED BY PUPPET
# ANY MANUAL CHANGES WILL BE LOST ON THE NEXT PUPPET RUN
# Executing foreman_scap_client from command line may be useful for debugging purposes.
# It may generate warnings due to a reference to a missing file.
# foreman_scap_client cron job
# Runs foreman_scap_client 1
0 1 * * 4 root /bin/sleep 165 ; /usr/bin/foreman_scap_client 1 2>&1 | logger -t foreman_scap_client
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.