Actions
Bug #23836
closed
Event log migration should not be done every time
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:
No
Description
Currently the database migration to update null values and add constraints to the nullable columns is run every time at startup. We want to run them only if we have not already done the migration : if the column is still nullable.
Also, in case of an error, the log should incite the user to send the details of the error for us to resolve it later.
Updated by Clark ANDRIANASOLO about 1 year ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO about 1 year ago
Work in progess here: https://github.com/clarktsiory/rudder/commit/90fb89750c147d0c87eb4e02d94d7a53c6a15ae5
Updated by Clark ANDRIANASOLO about 1 year ago
Work in progess here: https://github.com/clarktsiory/rudder/commit/8cc0710ba6e5d41b9726a5c175b9d13b40202825
Updated by Clark ANDRIANASOLO about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5232
Updated by Clark ANDRIANASOLO about 1 year ago
- Related to Bug #23699: Event log migration takes too long added
Updated by Clark ANDRIANASOLO about 1 year ago
- Related to Bug #19317: Last modified attribute of change request is always "unknown" added
Updated by Clark ANDRIANASOLO about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d9446f67960ea69e2f694ab31b1ac8ad9ada511a.
Updated by Vincent MEMBRÉ about 1 year ago
- Fix check changed from To do to Error - Fixed
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.10 and 8.0.4 which were released today.
Actions