Wow, thanks, this worked great for me. In case it helps others, here are
the commands in more detail:
# Connect to postgresql
psql -h localhost -d puppetdb -U puppetdb -W
# The psql prompt
puppetdb=> delete from reports where end_time > current_timestamp;
# Disconnect
puppetdb=> \q
On Wednesday,
Hey Ryan,
That makes sense, though I'd guess that new reports are being stored and
are available through the API, they just aren't reflected as "latest"
since that's determined by the end_time stamp. report-ttl will be
ineffective without resetting to the future, and then you'd be deleting
r
I have some systems that were deliberately changed to a time in the future
for testing, then changed back to normal when done. They work with puppet
fine now, but their puppetdb reports have timestamps in the future and new
reports will not be added. They show up in puppetboard with the inaccura
