Invoking a naming conflict as a result of 2 adds with same DN, but for example with different attribute values leaves DIT inconsistent.
- Stop replication between the servers.
- Add entry in M1
- Add entry in M2
- Re-enable replication between the 2 servers M1 and M2
- Search shows that we have 2 different entries, each with a conflict entry.
- The conflict is flagged as unresolved.
But it would be also nice to be able to solve the inconsistency in the DIT between the 2 servers.