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/<HOSTNAME>/<DATE>.yaml unfortunately, with a moderatly sized cluster (about 30 nodes), this fills-up very fast. For me, the reports folder was 52 GBytes, leading to a disk full (as my puppet-master was running on a small-ish VM). Of course, once the disk is full, absolutely nothing works anymore (new nodes get their certs saved as zero bytes, etc.). What should be done, is clean old reports, let's say those that are at least one month old, using a cron.daily job. I believe this should be fixed in both Stretch and Buster if possible. Cheers, Thomas Goirand (zigo)
