389-ds-base

#607 Replication issue: Entry can diverge betwen servers
Closed: wontfix Opened by tbordaz.

Closed: wontfix
Reopen Issue

With the following test case we can create an entry that has not the same attribute values on two servers.

Setup a 2 Masters topology, update the attached script and run it. The values of 'mail' are different on M1 vs M2

As a first approach I think that we sometime (always ?) fail to increase the subnumber of the CSN, so that we are not able to resolve the final status on non primary server.

Script to run to reproduce the bug. Run after creating a 2 MMR topology
do_bugreplication

I cannot reproduce inconsistency on the different servers. What I can reproduce is different behaviour with openldap and mozldap clients, where the behaviour of mozldap seems to incorrect at least unexpected. The reasonis that mozldap does accumulate the same opeartion types and so
the original:

changetype: modify
add: mail
mail: value1
-
delete: mail
-
add: mail
mail: value2

modifiy request will be sent as:
changetype: modify
add: mail
mail: value1
mail: value2
-
delete: mail

If you can reproduce an inconsistency on different servers can you add the entrywsi output

'''Here is the current status'''

  • I erroneously opened that ticket. Ludwig was right on his update, the reported problem is not reproducible.[[BR]]
    After (March 21st) his update I verified I was successful to reproduce it. But now I fail to reproduce.
    At first I thought a later fix fixed that bug, but even if I rebase earlier than March 21st (on master/1.3.1/1.3.0/1.2.11) I still fail to reproduce. So the most probable explanation is that I did twice the same diagnostic error (when opening the ticket and when retesting it).

'''Here are the next steps'''

  • being not able to reproduce this bug, on branches master,1.3.1,1.3.0 and 1.2.11. I close it as 'not a but'

Metadata Update from @tbordaz:
- Issue assigned to tbordaz
- Issue set to the milestone: 1.3.2 - 08/13 (August)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/607

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)
Metadata
None
None
None
Normal
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.