Bug #8444
closedNodeConfigurations and reportsexecutions are not archived in the same way as reports
Description
We keep expected reports and reportsexecution in the database for as long as the archived reports - however there are no way to correlate both (once reports are in archivedruddersysevent, we don't query them anymore in the web interface).
We should purge them when reports are archived, as it would gain a lot of space on big installation, and lower pressure on database
Updated by Nicolas CHARLES about 8 years ago
This ticket if for branch 2.11, with only expeectedreports
Updated by Nicolas CHARLES about 8 years ago
Nicolas CHARLES wrote:
This ticket if for branch 2.11, with only expeectedreports
ha, actually, reportsexecutions is also present in 2.11 :)
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Jonathan CLARKE about 8 years ago
- Subject changed from Expectedreports and reportsexecutions are deleted only where we delete reports from archived reports to Expectedreports and reportsexecutions are not archived in the same was as reports
- Assignee set to Nicolas CHARLES
- Target version changed from 2.11.23 to 4.0.0~rc2
Updated by François ARMAND almost 8 years ago
- Subject changed from Expectedreports and reportsexecutions are not archived in the same was as reports to NodeConfigurations and reportsexecutions are not archived in the same way as reports
- Target version changed from 4.0.0~rc2 to 321
This need to be done in first minor for 4.0.
Updated by Nicolas CHARLES almost 8 years ago
Actually, since table expectedreports have been removed, the batch fails, and it need to be done for release 4.0.0
Updated by Nicolas CHARLES almost 8 years ago
- Target version changed from 321 to 4.0.0~rc5
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1348
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|096aa9bea25fe7d44b4fc13891ad133d02908ed3.
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.