Comment 5 for bug 1581098

Revision history for this message
Dmitry Burmistrov (dmburmistrov) wrote : Re: [mos-xenial] logrotate for puppet.log should contain "su" setting

As we can see here https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack/files/logrotate-puppet.conf
We don't rotate "/var/log/puppet-error.log" file. This is about 9.X (ex. 10.0).

The similar issue is in earlier Mitaka release (9.0) - we don't rotate "puppet-error.log" and "su" option is missing.
[root@nailgun ~]# cat /etc/fuel_release
9.0
[root@nailgun ~]# cat /etc/fuel_build_id
395

root@node-27:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty
root@node-27:~# ls -l /var/log/puppet*
-rw-r--r-- 1 root root 0 Jul 5 08:39 /var/log/puppet-error.log
-rw------- 1 puppet puppet 416956 Jul 5 11:36 /var/log/puppet.log

/var/log/puppet:
total 0
root@node-27:~# fgrep puppet -R /etc/logr*
/etc/logrotate.d/fuel.nodaily:# managed by puppet
/etc/logrotate.d/puppet:/var/log/puppet.log {
/etc/logrotate.d/puppet: create 0600 puppet puppet
/etc/logrotate.d/apache2:# This file managed via puppet
root@node-27:~# logrotate -f /etc/logrotate.d/puppet
error: skipping "/var/log/puppet.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.