Bug 1286027 - Puppet can't write to /var/log/foreman/cron.log
Summary: Puppet can't write to /var/log/foreman/cron.log
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.1.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-27 09:42 UTC by Kamudini Gazdikova
Modified: 2020-07-16 08:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:03:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16944 0 Normal New Puppet can't write to /var/log/foreman/cron.log 2020-02-12 20:20:26 UTC

Description Kamudini Gazdikova 2015-11-27 09:42:42 UTC
Description of problem:
Puppet can't write to /var/log/foreman/cron.log

Version-Release number of selected component (if applicable):
Red Hat Satellite v.6.1.x

Issue :  puppet can't write to /var/log/foreman/cron.log

As customer observed :

For the below line in /etc/cron.d/foreman:

*/2 * * * *     puppet    /usr/bin/ruby193-ruby /etc/puppet/node.rb --push-facts >>/var/log/foreman/cron.log 2>&1

The log file '/var/log/foreman/cron.log' was not writeable an email with the error message was send by crond to user puppet.

Workaround:

Resolved by doing,

# usermod -aG foreman puppet

and

# chmod g+w /var/log/foreman/cron.log

Comment 1 Bryan Kearney 2016-07-26 19:09:29 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Stephen Benjamin 2016-10-14 14:06:55 UTC
Created redmine issue http://projects.theforeman.org/issues/16944 from this bug

Comment 5 Stephen Benjamin 2016-10-14 14:08:25 UTC
Cron job is in the packaging repo.

Comment 6 Bryan Kearney 2018-09-04 18:03:59 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.