https://bugs.openldap.org/show_bug.cgi?id=10369
--- Comment #8 from elecharny@apache.org --- The config is not a human generated Ldif. It’s a old config file converted to slapd.d I can’t check how it gets generated now (in my car), but will provide the info.
I understand how that can be a burden to fix as you want to keep a compatibility with pre 2.4 config format, so keeping both MirrorMode and MultiProvider attributes. The main issue is having both in the same config, and I tend to think that if it’s the case, then mirror mode should simply be ignored when processing the config in slapd (but kept as a visible attribute): - if mirrorMode *or* multiProvider are present, then they are treated as is. - if *both* are present, then multiProvider should be the only one used to configure slapd, mirror mode being ignored.
In any case, it’s far from being critical, and a simple warning while processing the config should do the trick (plus maybe a mention in the slapd man page explaining that mirrorMode is obsolete.
From my PoV, now that I understand what’s going on, I’m fine with whatever choice is made, as soon as the issue has been tracked for everyone having the same pb in the future (assuming they check the bug tracker).