this is a special type of conflict, also indicated by the "objectClass: glue". It is created if an entry is deleted on one server and at the same time a child for this entry is created on another server. when both operations are replicated a conflict arises. On on eserver it would be the attempt to delete an entry with children and on the other an attempt to add an entry without parent. This is resolved by resurrecting the deleted entry and flagging it as conflict and adding an objectclass glue.This is a new one, any ideas on how to get this to sync?
ldapsearch -x -D "cn=directory manager" -W -b "dc=ipa,dc=example,dc=com" "nsds5ReplConflict=*" \* nsds5ReplConflictEnter LDAP Password:# extended LDIF## LDAPv3# base <dc=ipa,dc=example,dc=com> with scope subtree# filter: nsds5ReplConflict=*# requesting: * nsds5ReplConflict#
# servers, dns, ipa.example.comdn: cn=servers,cn=dns,dc=ipa,dc=example,dc=comobjectClass: topobjectClass: extensibleObjectobjectClass: gluecn: serversnsds5ReplConflict: missingEntry
# search resultsearch: 2result: 0 Success
# numResponses: 2
_______________________________________________ FreeIPA-users mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com
-- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander