Thomas Goirand writes:
> Using puppet-master from both Stretch and Buster in production, I have found
> out that on each puppet run, a run report is saved under:
>
> /var/lib/puppet/reports//.yaml
>
> unfortunately, with a moderatly sized cluster (about 30 nodes), this fills-up
> very fast. For m
I've also encountered this bug in the past when my master filled up a
hard-drive with reports.
You can easily turn reports off in the puppet.conf file, but I agree it
would be nice if a cronjob ran and removed old reports.
I don't think turning reports off by default is a good fix though, as it
c
Package: puppet-master
Version: 5.5.10-2
Severity: important
Dear maintainer(s),
Using puppet-master from both Stretch and Buster in production, I have found
out that on each puppet run, a run report is saved under:
/var/lib/puppet/reports//.yaml
unfortunately, with a moderatly sized cluster (a
3 matches
Mail list logo
