-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logrotate config defaults #118
Comments
I'm having the same issue with Puppet 6 and v3.4.0 of this module. clsvegar@test02:~$ /opt/puppetlabs/bin/puppet --version
6.0.4
clsvegar@test02:~$ sudo /opt/puppetlabs/bin/puppet module list | grep logrotate
├── puppet-logrotate (v3.4.0) I have this config in Hiera, and none of the default logrotate::config:
dateext: true
dateformat: '.upto-%Y%m%d'
compress: true
delaycompress: true To have a working config, I have to add these lines as well: su: true
su_user: 'root'
su_group: 'syslog' |
I'm having this same problem since I updated from version 3.3.0 to 3.4.0. |
Hey @vegarnilsen or @amateo, could you provide a PR with a fix for this? |
After a lot of time... The problem is with the code in
This if isn't matched when you have
in |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
Sensible OS defaults from https://github.com/voxpupuli/puppet-logrotate/blob/master/manifests/params.pp are not applied anymore if any
config
is specified. These defaults are crucial at least on Ubuntu, wheresu_user
andsu_group
are essential.What behaviour did you expect instead
I expected the defaults to be used as base, extended / overwritable with user options, i.e.:
I'm using now as workaround exactly that, preceded by:
i.e. using the params class manually.
The text was updated successfully, but these errors were encountered: