Actions
Bug #13406
closed
Race condition on reinstall of packages triggers re-conversion of old LDAP BDB files to LMDB
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
-
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
63
Name check:
Fix check:
Regression:
Description
Conditions are still unknown, end result is kinda unfavourable, or in other words, fatal (from data loss of rudder config parts to worse things)
It is hard to find the specifics, I would assume that for this to happen the old files still need to be around.
I assume it's also something env-specific and that this cannot be triggered without specific conditions, aka very bad luck.
I suggest issuing a periodic warning (/var/log/messages at very least) if BDB files are found on any modern Rudder install.
(independent of making sure they are deleted on LMDB switch etc. etc.
They could still be around for some reason, i.e. a prior failed update. The risk is in the existance of the old config info, not in the part that is processing it)
Updated by
Actions