Actions
Bug #9322
closedSome runs have no report on ncf if after upgrading from 3.1.13
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
In Rudder 3.1.13, reports files were not correctly purged, so there are potentially a lot of reports files with different PID
When upgrading to latest version, the files are correctly purged after each run, and the dandling files after x days
It is possible, if reports files did not change, that there is a collision during the x days interval, and tmp and res files are not updated (because they are already correct)
Since reporting depend on the _repaired class, and the result is _kept, no report is made
Note: this is super random, and highly confusing
Actions