Actions
Bug #3917
closedArchiving reports should not break on on duplicate IDs or key
Status:
Rejected
Priority:
2
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When Rudder automatically archives reports, it does it in 3 step:
- copy from ruddersysevents to archivedreports
- delete from ruddersysevents
- vaccumm
If the webapp is stopped between 1 and 2, we have the archive in an invalid state, causing it to fail later as it tries to insert already existing entries into the archivedruddersysevents.
In fact, we want to be able to have the archived execution reports on an other DB, so we don't want to add transaction, but be smart about how we handle already migrated reports.
Updated by François ARMAND over 11 years ago
- Subject changed from The reports archive are not transactionnal to Archiving reports should not break on on duplicate IDs or key
- Description updated (diff)
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.6.6 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.6.7
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.6.7 to 2.6.8
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.6.8 to 2.6.9
Updated by Nicolas PERRON about 11 years ago
- Priority changed from N/A to 2
- Target version changed from 2.6.9 to 2.6.10
It seems important.
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.6.10 to 2.6.11
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.6.11 to 2.6.12
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.6.12 to 2.6.13
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.13 to 2.6.14
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.14 to 2.6.16
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.16 to 2.6.17
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.6.17 to 2.6.18
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 2.6.18 to 2.6.19
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.6.19 to 2.6.20
Updated by François ARMAND almost 10 years ago
- Assignee set to Nicolas CHARLES
- Target version changed from 2.6.20 to 2.10.10
Nico, I think it's not more the case in 2.10. Could you confirm, and if so closed the ticket ?
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.10 to 2.10.11
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.11 to 2.10.12
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.12 to 2.10.13
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.13 to 2.10.14
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.14 to 2.10.15
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.15 to 2.10.16
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.16 to 2.10.17
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.17 to 2.10.18
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.18 to 2.10.19
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.19 to 2.10.20
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.20 to 2.11.18
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by François ARMAND over 7 years ago
- Has duplicate Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again added
Updated by François ARMAND over 7 years ago
- Has duplicate deleted (Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again)
Updated by François ARMAND over 7 years ago
- Is duplicate of Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again added
Updated by François ARMAND over 7 years ago
- Status changed from New to Rejected
This was corrected in #10171
Actions