Bug 1395848 - segments should not be added under a replication conflict in cn=topology subtree.
Summary: segments should not be added under a replication conflict in cn=topology subt...
Status: CLOSED DUPLICATE of bug 1274430
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Depends On: 1398670
TreeView+ depends on / blocked
Reported: 2016-11-16 20:01 UTC by German Parente
Modified: 2017-04-07 09:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-04-07 09:11:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description German Parente 2016-11-16 20:01:31 UTC
Description of problem:

I have not been able to reproduce this issue yet. I think a simple scenario to reproduce it is to update to 7.3 (domain level 1) two nodes at the same time which are temporarily disconnected regarding replication.

What we observe is that one or more conflicts could appear to these entries:

dn: cn=domain,cn=topology,cn=ipa,cn=etc,<suffix>
dn: cn=ca,cn=topology,cn=ipa,cn=etc,<suffix>

like for instance:

dn: cn=domain+nsuniqueid=b3725a7b-a34711e6-b68bc5e1-98fbe70f,cn=topology,cn=ipa,cn=etc,<suffix>
dn: cn=ca+nsuniqueid=b3725abf-a34711e6-b68bc5e1-98fbe70f,cn=topology,cn=ipa,cn=etc,<suffix>
Which could unfortunately happen.

The problem is that afterwards we can find segments created under the conflicts:

dn: cn=<host1>-to-<host2>,cn=domain+nsuniqueid=b3725a7b-a34711e6-b68bc5e1-98fbe70f,cn=topology,cn=ipa,cn=etc,<suffix>

we could eventually rename the entry but we have also segments created under the original entry:

dn: cn=<host3>-to-<host4>,cn=domain,cn=topology,cn=ipa,cn=etc,<suffix>

This bug is reported to get sure that applications check that there's a replication conflict and create the segment always out of that conflict.

This could also be related to bz's:

[RFE] Make replication plugin put conflicts in a special suffix 


 [RFE] it could be nice to have replication conflicts being skipped in client app queries. 

Thanks and regards,


Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 6 Ludwig 2017-04-07 09:11:46 UTC
this bug will be resolved with the general repl conflict fix tracked in 1274430

*** This bug has been marked as a duplicate of bug 1274430 ***

Note You need to log in before you can comment on or make changes to this bug.