Bug #13406
closed
Race condition on reinstall of packages triggers re-conversion of old LDAP BDB files to LMDB
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 François ARMAND over 5 years ago
So. We discussed that online too, and it's hard and we don't know for now what went wrong and how. It is critical (but IIRC, the correct archive was restored afterwards).
We are looking to implement the proposed mitigation solution (i.e: don't try to use very old archive if not explicitly asked for). And we are trying to check if some missing piece of old bdb upgrade were left in some rarely used code path.
Updated by François ARMAND over 5 years ago
- Status changed from New to Rejected
- Priority changed from 65 to 63
We are going to close that one because it can only happen for new people on 4.0/4.1, which are few, and we don't have sufficient information to progress on a solution.
Moreover, the conversion logic was totally removed in 4.3, and there is no way it could happen since then.