Bug #25830
closed
Bug #25782: Bad postgresql time conversion for event log cleaning
Bad postgresql time conversion for event log cleaning in 8.1
Added by Clark ANDRIANASOLO 17 days ago.
Updated 16 days ago.
Category:
Web - Nodes & inventories
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Description
Backporting parent ticket in 8.1 since in the database the dates are written using the doobie JSON codec, so with ISO8601, it is the case since 8.0.
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/6000
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
I changed the CRON to every second :
rudder.inventories.cleanup.old.files.cron=* * * * * ?
and I got the log for the successful deletion :
2024-11-07 12:07:34+0100 INFO inventory-processing - Deleted historical pending inventory information of nodes: 'e98a11f8-7516-4775-b51f-69532733e815', '51c64363-a2b1-47fe-af20-12e6d211c2be'
for two nodes I have deleted at earlier dates in a 8.1 environment :
>> psql -h localhost -U rudder rudder -c "select deleteEvent->>'date' from nodefacts"
?column?
---------------------------
2024-09-27T07:40:04Z
2024-11-06T18:31:57+01:00
(2 rows)
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by