This bug is created as a clone of upstream ticket:
I'm testing 389 v22.214.171.124 on CentOS 5.8 x86_64. With Attribute Uniqueness plugin enabled for one of the attributes of the entry (not the naming attribute) modrdn operation for this entry fails with:
ldap_rename: Constraint violation (19)
additional info: Another entry with the same attribute value already exists (attribute: "X-UniqueId")
In our case we need the uniqueness of the X-UniqueId attribute. The modrdn was changing the uid attribute. In the latest version of 1.2.9.x this problem did not exist.
It's a blocking issue for the upgrade 1.2.9.x->1.2.10x on our production servers.
Typical log trace:
''[11/Jul/2012:16:20:40 +0200] conn=5 op=6 MODRDN dn="uid=somelogin,ou=Personnel,ou=Utilisateurs,dc=id,dc=polytechnique,dc=edu" newrdn="uid=somelogin.test" newsuperior="ou=Personnel,ou=Utilisateurs,dc=id,dc=polytechnique,dc=edu"
[11/Jul/2012:16:20:41 +0200] conn=5 op=6 RESULT err=19 tag=109 nentries=0 etime=0.012000
r6731 | rmeggins@REDHAT.COM | 2012-07-13 16:05:21 -0600 (Fri, 13 Jul 2012) | 5 lines
Bug 840153 - Impossible to rename entry (modrdn) with Attribute Uniqueness plugin enabled
Added tests - the tests are the ic5X tests - these tests verify the bug is
fixed and test other aspects of modrdn with attribute uniqueness enabled
Uid startup 100% (1/1)
Uid run 100% (9/9)
Uid cleanup 100% (1/1)
All tests passed in the acceptance with 389-ds-base.x86_64 0:126.96.36.199-10.el6 build on rhel64.
Hence marking bug as VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.