Actions
Bug #10171
closedIf the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Reports archiving happens by default every day.
It's a 3 steps procedure, with:
It's a 3 steps procedure, with:
- reports insertion into archivedruddersysevents from ruddersysevents
- deletion from ruddersysevents
- vaccuum
If this is interupted during step 2, then reports already moved will not be deleted, and on the following day they won't be archived (because of duplicate keys)
We should have a more robust system that would recover from where it stopped
(alternatives are to drop the unicity constraints on archivedruddersysevents, but this would lead to duplicate entries in this case)
Actions