Issue 132 - ITS78 not fixed - modrdn loses records
Summary: ITS78 not fixed - modrdn loses records
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-04-19 19:05 UTC by asparks@quris.com
Modified: 2014-08-01 21:06 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description asparks@quris.com 1999-04-19 19:05:01 UTC
Full_Name: Alan Sparks
Version: OpenLDAP 1.2.1
OS: HP/UX 10.20
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (151.114.2.18)


ITS #78 marked closed, but not fixed.  Duplicated the problem as still
existent in OpenLDAP 1.2.1.  Compiled w/ GCC 2.8.1 on HP/UX 10.20 using
either Sleepycat 2.3.16 or 2.7.4.

After changing RDN of entry (in my case,
from cn=Partners WorldCom Access,ou=Groups,o=Harris/NSS
to cn=Partners MCIWorldCom Access,ou=Groups,o=Harris/NSS) with a delete-old-rdn
parameter, subsequent ldapsearch cannot find the updated entry.  Entry
reappears
after slapd restart.

Bad news. :-(
Comment 1 Juan Carlos Gomez 1999-04-19 20:35:34 UTC
asparks@nss.harris.com wrote:

> Full_Name: Alan Sparks
> Version: OpenLDAP 1.2.1
> OS: HP/UX 10.20
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (151.114.2.18)
>
> ITS #78 marked closed, but not fixed.  Duplicated the problem as still
> existent in OpenLDAP 1.2.1.  Compiled w/ GCC 2.8.1 on HP/UX 10.20 using
> either Sleepycat 2.3.16 or 2.7.4.
>
> After changing RDN of entry (in my case,
> from cn=Partners WorldCom Access,ou=Groups,o=Harris/NSS
> to cn=Partners MCIWorldCom Access,ou=Groups,o=Harris/NSS) with a delete-old-rdn
> parameter, subsequent ldapsearch cannot find the updated entry.  Entry
> reappears
> after slapd restart.
>
> Bad news. :-(

  Someone else just reported the same problem....seems to be an extra space is
getting
introduced in the dn at the index entry. Will take care of this as soon as I get
some
time off. Thanks for reporting it.

                                                        Juan


Comment 2 gomez@openldap.org 1999-04-19 21:14:30 UTC
changed notes
moved from Incoming to Software Bugs
Comment 3 gomez@openldap.org 1999-04-20 00:23:05 UTC
changed notes
Comment 4 Juan Carlos Gomez 1999-04-20 01:29:30 UTC
A fix has been posted to the devel distribution for the problem you and others
reported. The problems was that index files were not being updated correctly
after modrdn operations. I believe there is still a problem: if you use modrdn
with deleteoldrdn=1, the old attribute value (rdn) will be deleted but a search
with the oldrdn will still return the entry. I would very likely fix this in the
near
future after I get approval from others in core.

Please test and send your feedback!

                                                                        Enjoy,
Juan


asparks@nss.harris.com wrote:

> Full_Name: Alan Sparks
> Version: OpenLDAP 1.2.1
> OS: HP/UX 10.20
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (151.114.2.18)
>
> ITS #78 marked closed, but not fixed.  Duplicated the problem as still
> existent in OpenLDAP 1.2.1.  Compiled w/ GCC 2.8.1 on HP/UX 10.20 using
> either Sleepycat 2.3.16 or 2.7.4.
>
> After changing RDN of entry (in my case,
> from cn=Partners WorldCom Access,ou=Groups,o=Harris/NSS
> to cn=Partners MCIWorldCom Access,ou=Groups,o=Harris/NSS) with a delete-old-rdn
> parameter, subsequent ldapsearch cannot find the updated entry.  Entry
> reappears
> after slapd restart.
>
> Bad news. :-(



Comment 5 gomez@openldap.org 1999-04-20 01:33:19 UTC
changed notes
changed state Open to Test
Comment 6 dbadrak@census.gov 1999-04-22 19:39:55 UTC
Juan,

On Tue, 20 Apr 1999 gomez@cthulhu.engr.sgi.com wrote:

> A fix has been posted to the devel distribution for the problem you and others
> reported. The problems was that index files were not being updated correctly
> after modrdn operations. I believe there is still a problem: if you use modrdn
> with deleteoldrdn=1, the old attribute value (rdn) will be deleted but a search
> with the oldrdn will still return the entry. I would very likely fix this in the
> near
> future after I get approval from others in core.

I'm having some troubles trying to get a patch out of -devel to 1.2.1.  I
want to patch the 1.2.1 source and try this, but there's all this new
stuff in the -devel CVS.

How can I get a diff file for openldap 1.2.1 stable to fix this?

Thanks.

Don 
-- 
Don Badrak <dbadrak@census.gov>              301.457.8263 work
Telecommunications Office		     301.457.4438 fax
U.S. Bureau of the Census
Suitland MD, USA

Comment 7 Kurt Zeilenga 1999-05-25 00:02:53 UTC
changed notes
Comment 8 Kurt Zeilenga 1999-05-25 00:03:20 UTC
changed notes
changed state Test to Release
Comment 9 Kurt Zeilenga 1999-06-01 17:58:56 UTC
changed notes
changed state Release to Closed
Comment 10 OpenLDAP project 2014-08-01 21:06:52 UTC
Fixes applied to -devel and re12.