Le 2024-09-10 à 17 h 21, Jonathan Wiltshire a écrit :
Control: tag -1 confirmed
On Tue, Sep 10, 2024 at 05:11:40PM -0400, Jérôme Charaoui wrote:
Le 2024-09-10 à 15 h 48, Jonathan Wiltshire a écrit :
Control: tag -1 moreinfo
Hi,
On Thu, Sep 05, 2024 at 10:18:15PM -0400, Jérôme Charaoui wrote:
This is causing some installations that were upgraded from bullseye to
bookworm to break after some time because of the large amounts of reports
generated and stored on the Puppet server. An example of this is
https://bugs.debian.org/1078911
How does this interact with the puppetdb setting report-ttl?
(https://www.puppet.com/docs/puppetdb/7/maintain_and_tune.html#clean-up-old-reports)
There is no interaction: when reports are sent to PuppetDB ("reports =
puppetdb" in /etc/puppet/puppet.conf), they're stored in database backend,
typically PostgreSQL. The "report-ttl" setting is independent and affects
only those reports which are stored in the database.
In that case please added Closes for any applicable bugs and go ahead with
the upload.
Thank you.
Should Closes still be added for a bug that was closed by an upload to
unstable that addressed the bug in another manner? I'm referring here to
https://bugs.debian.org/1080489
-- Jérôme
