Project

General

Profile

Actions
Copy link

Feature #21389

closed

Add a header into a cron file on client

Added by Ondřej Pražák over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1489252
Pull request:
https://github.com/theforeman/puppet-foreman_scap_client/pull/41
Fixed in Releases:
puppet-foreman_scap_client 0.3.19
Found in Releases:
Red Hat JIRA:

Description

Running foreman_scap_client manually shows warnings from oscap scanner
when external files are referenced since foreman_scap_client does not support
downloading external resources.

The warnings are not shown anywhere since the foreman_scap_client runs from a cron.
Running foreman_scap_client manually can be used as part of troubleshooting or users
can find out the command by themselves by inspecting the cron file and when the warning
is shown, it may seem like there is a problem that needs to be addressed.

We can add a header to the cron file explaining the nature of these warnings and that
they do not hint at a serious problem.

Suggested header:

  1. HEADER: This file was autogenerated at 2017-01-09 07:56:17 +0000 by puppet.
  2. HEADER: While it can still be managed manually, it is definitely not recommended.
  3. HEADER: Manually executing foreman_scap_client manually may generate warnings
    due to a reference to a missing file.
Actions
Copy link
 #1

Updated by Marek Hulán over 6 years ago

  • Subject changed from Add a header into a cron file on client to Add a header into a cron file on client
  • Status changed from New to Closed
  • Pull request https://github.com/theforeman/puppet-foreman_scap_client/pull/41 added
Actions
Copy link
 #2

Updated by Marek Hulán over 5 years ago

  • Fixed in Releases puppet-foreman_scap_client 0.3.19 added
Actions
Copy link

Also available in: Atom PDF