Actions
Bug #16839
closed
Restoring directive archive timeout and break LDAP
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
76
Name check:
To do
Fix check:
Checked
Regression:
Description
When restauring directive archive, if the operation takes more than 5s (for ex b/c there's a lot of directives, or the unerlying LDAP or I/O are slow), then the restauration is (violently) interrupted, letting corrupted data in LDAP.
This is specific to 6.0.3 and a regression from other rudder version.
Updated by François ARMAND about 4 years ago
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2798
Updated by François ARMAND about 4 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|15fc69f1ebdd8e5a54dc3f6ba1d472f72e5ec640.
Updated by Vincent MEMBRÉ about 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.4 which was released today.
Actions