You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 7.15.0, server 7.6.1
Ruby: 2.7.5
Distribution: Ubuntu 18.04.6 LTS
Module version: 8.1.0
How to reproduce (e.g Puppet code you use)
Thanks for a great module BTW.
puppet 7.6 or 7.6.1 or introduced a warning when a File resource affects more than 1000 files by default. The puppetboard module trips over the limit and produces a warning because of the number of files in the puppetboard repository.
max_files defaults to 0 (issues a warning). I added the attribute with a value -1 which disables the warning. You might want to choose a different value, but that may cause the resource to fail at some later time when the files in the repo exceed the limit.
I have a slightly unusual puppetboard setup managed by puppet because I couldn't at the time figure out to make the puppetboard module manage the apache vhost with SSL certificate authentication. The apache portion of the configuration is is not relevant to the warning but I've included it anyway.
root@puppetdb01:/etc/puppetlabs/puppetdb/conf.d# puppet agent -t
Info: Using environment 'infrastructure'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for puppetdb01.xxxxxx.com
Info: Applying configuration version '1648231182'
Warning: The directory '/srv/puppetboard/puppetboard' contains 1936 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for max_files parameter or consider using an alternate method to manage large directory trees
What behaviour did you expect instead
No warning.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered:
Instead of cloning as root and using a file resource to change files
ownership to the configured user, directly clone the repository with
this user.
This fix a warning issued by puppet:
Warning: The directory '/srv/puppetboard/puppetboard' contains 1936 entries, which exceeds the default soft limit 1000
Fixes#351
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Thanks for a great module BTW.
puppet 7.6 or 7.6.1 or introduced a warning when a File resource affects more than 1000 files by default. The puppetboard module trips over the limit and produces a warning because of the number of files in the puppetboard repository.
puppetboard/manifests/init.pp at line 224:
max_files defaults to 0 (issues a warning). I added the attribute with a value -1 which disables the warning. You might want to choose a different value, but that may cause the resource to fail at some later time when the files in the repo exceed the limit.
I have a slightly unusual puppetboard setup managed by puppet because I couldn't at the time figure out to make the puppetboard module manage the apache vhost with SSL certificate authentication. The apache portion of the configuration is is not relevant to the warning but I've included it anyway.
What are you seeing
root@puppetdb01:/etc/puppetlabs/puppetdb/conf.d# puppet agent -t
Info: Using environment 'infrastructure'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for puppetdb01.xxxxxx.com
Info: Applying configuration version '1648231182'
Warning: The directory '/srv/puppetboard/puppetboard' contains 1936 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for
max_files
parameter or consider using an alternate method to manage large directory treesWhat behaviour did you expect instead
No warning.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: