Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Enable syncrepl for openldap-server slapd with any back end 2. Connect to the syncrepl provider with a consumer 3. Modify an autofs (for example) entry on the provider. Actual results: Oct 4 16:53:18 auth1 slapd[2712]: <= str2entry(ou=auto.import,dc=dcs,dc=qmul,dc=ac,dc=uk) -> 0x555555aecea0 Oct 4 16:53:18 auth1 slapd[2712]: <= id2entry_w( 80 ) 0x555555aecea0 (disk) Oct 4 16:53:18 auth1 slapd[2712]: ldbm_back_modrdn: wr to children of entry ou=auto.import,dc=dcs,dc=qmul,dc=ac,dc=uk OK Oct 4 16:53:18 auth1 slapd[2712]: ldbm_back_modrdn: parent dn=ou=auto.import,dc=dcs,dc=qmul,dc=ac,dc=uk Oct 4 16:53:18 auth1 slapd[2712]: ldbm_back_modrdn: new parent "*" requested... Oct 4 16:53:18 auth1 slapd[2712]: dn2entry_w: dn: "�UUU" Oct 4 16:53:18 auth1 slapd[2712]: => dn2id( "�UUU" ) Oct 4 16:53:18 auth1 slapd[2712]: => ldbm_cache_open( "dn2id.dbb", 73, 600 ) Oct 4 16:53:18 auth1 slapd[2712]: <= ldbm_cache_open (cache 0) Oct 4 16:53:18 auth1 slapd[2712]: <= dn2id NOID Oct 4 16:53:18 auth1 slapd[2712]: ldbm_back_modrdn: newSup(ndn=�UUU) not here! Expected results: The above but returning null rather than garbage at "Oct 4 16:53:18 auth1 slapd[2712]: ldbm_back_modrdn: new parent "*" requested..." Additional info: This has been fixed upstream in openldap 2.3.27 CVS
Created attachment 137831 [details] Diff file for syncrepl.c
This bug also exists in FC5 openldap-servers-2.3.19
And in FC6 release. I assume the fix is in 2.3.28 stable if you're waiting for an upstream fix.......
Is anyone working on this bug?
Does anyone else think that two months without even an acknowledgement is unacceptable? I would have thought this was a simple open-and-shut case. If bugzilla isn't the right place for reporting bugs, where is?
It's now been comfortably over six months. WHY IS NOBODY RESPONDING? You've even got the fix. Sigh..
openldap-2.3.30-2.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.