Consider the case where you have a single valued attribute that is loaded in from a db2ldif -r file that looks like this:
dn: some entry ... svattr;adcsn-XXXX;vdcsn-XXXX;deletedattribute;deleted:
Note - there is nothing after the ":" above, just a new line.
Load this in on both a master and a replica. Next, do an ADD operation to svattr on the master - it will work fine. However, the ADD operation will not be replicated to the replica.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1062763
0001-Ticket-47692-single-valued-attribute-replicated-ADD-.patch 0001-Ticket-47692-single-valued-attribute-replicated-ADD-.patch
To ssh://git.fedorahosted.org/git/389/ds.git 346d366..86fb137 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 86fb137 Author: Rich Megginson rmeggins@redhat.com Date: Fri Feb 7 16:02:37 2014 -0700 af85853..dad08c1 389-ds-base-1.3.0 -> 389-ds-base-1.3.0 commit dad08c10826896dc4e8772ec400d60e3eb0ebbb6 Author: Rich Megginson rmeggins@redhat.com Date: Fri Feb 7 16:02:37 2014 -0700 baa3df4..a4a4642 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit a4a4642 Author: Rich Megginson rmeggins@redhat.com Date: Fri Feb 7 16:02:37 2014 -0700 901dc5e..01a1121 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit 01a1121 Author: Rich Megginson rmeggins@redhat.com Date: Fri Feb 7 16:02:37 2014 -0700 80e39bc..59941ea master -> master commit 59941ea Author: Rich Megginson rmeggins@redhat.com Date: Fri Feb 7 16:02:37 2014 -0700
bad - previous fix was incomplete - reopening
0001-Ticket-47692-single-valued-attribute-replicated-ADD-.patch 0001-Ticket-47692-single-valued-attribute-replicated-ADD-.2.patch
To ssh://git.fedorahosted.org/git/389/ds.git d6d3731..1dbf87a 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 1dbf87a Author: Rich Megginson rmeggins@redhat.com Date: Thu Jul 10 14:18:06 2014 -0600 e260d9f..aead2be 389-ds-base-1.3.0 -> 389-ds-base-1.3.0 commit aead2be2a9cc5392713c7849c18a9bf218beb533 Author: Rich Megginson rmeggins@redhat.com Date: Thu Jul 10 14:18:06 2014 -0600 9bd67e2..45dcda2 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit 45dcda2425a865bf529ad0c8423664091392b865 Author: Rich Megginson rmeggins@redhat.com Date: Thu Jul 10 14:18:06 2014 -0600 5b46542..60d8bf9 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit 60d8bf9 Author: Rich Megginson rmeggins@redhat.com Date: Thu Jul 10 14:18:06 2014 -0600 e2c5505..4b54366 master -> master commit 4b54366 Author: Rich Megginson rmeggins@redhat.com Date: Thu Jul 10 14:18:06 2014 -0600
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.11.24
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/1028
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.