Actions
Bug #6011
closed
Bug #6005: If a node had a date in the future, but returned to current time, the reporting will always be invalid (until it catches up with the future date)
Execute the migration script for the change of table reports execution
Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In the parent ticket with updated the format of the database, we must run the migration script during the migration
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/568
Updated by Nicolas CHARLES almost 10 years ago
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset packages:rudder-packages|commit:5394b215b0b3121a70d28127be4189c07840acac.
Updated by Jonathan CLARKE almost 10 years ago
Applied in changeset packages:rudder-packages|commit:20253dc47a51032cfa0d692d21e4eca3ec685b21.
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions