[Date Prev][Date Next]
Re: (ITS#6987) cn=config renumbers indexes on startup without modrdn-ing them
> Full_Name: Ondrej Kuznik
> Version: HEAD
> OS: Linux
> Submission from: (NULL) (18.104.22.168)
> When storing cn=config entries whose rdns use different attributes, they
> may be
> received in a different order during startup. This will mess with their
> numbering and since a change like that is not anticipated in the code, it
> never pushed to the underlying database either.
> This leads to a state when the cn=config database and underlying on-disk
> representation are out of sync, making modification (and maybe deletion)
> of the
> affected entries impossible.
> If needed, I can create a minimal overlay showing these symptoms.
Please, do. I find this report quite unclear, as I could not understand
what the actual issue is.