#47778 backend transaction timing problems while renaming a subtree
Closed: Invalid None Opened 6 years ago by nhosoi.

Description of problem:
When renaming a subtree that contains group and user entries such as the users
are members of the groups, referential integrity plugin operation fails.

From Noriko's email:

I'm afraid this particular test case may not work with referential integrity
with the betxn timing.

This case renames ou=A,dc=suffix to ou=X,ou=Y,ou=Z,dc=suffix. And we have
users and groups in ou=A,dc=suffix with having the users as a member in the
groups. Please note that users are located prior to the groups.

If we rename ou=A,dc=suffix to ou=X,ou=Y,ou=Z,dc=suffix, its children are
renamed and it triggers the referential integrity plug-in (Let's say
uid=testuser). In the reverential integrity plug-in, it searches entries which
have the DN (uid=testuser,ou=A,dc=suffix) and it tries to replace it with a new
DN (uid=testuser,ou=X,ou=Y,ou=Z,dc=suffix). But the found group entry's DN is
still an old one (cn=testgroup,ou=A,dc=suffix). And modifying the entry is
failing in the test case due to no such entry (LDAP_NO_SUCH_OBJECT).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a (large) number of entries as groups and members of these groups.
2. Rename the subtree as in description


Can you please clarify the testcase?

I setup:


Added 5 users under ou=A
Added a group under ou=A, and added those 5 users

Then I did the modrdn:

dn: ou=A,dc=example,dc=com
changetype: modrdn
newrdn: ou=X
deleteoldrdn: 1
newsuperior: ou=Y,ou=Z,dc=example,dc=com

resulting in "ou=A,dc=example,dc=com" => "ou=X,ou=Y,ou=Z,dc=example,dc=com"

Everything looks good after this operation. The group does contain the correct/new member values, and if I delete a user it is removed from the group.

Is there something I'm missing?


Hi Mark, please take a look at bz1082542. I'm clearing "needinfo" flag for now. (Please feel free to set it if you need more info...)

Hi Mark, I also could not reproduce the problem on the multiple combinations... (see the bug)

Closing since this can not be reproduced now...

Metadata Update from @nhosoi:
- Issue assigned to mreynolds
- Issue set to the milestone:

3 years ago

Login to comment on this ticket.