#48637 ADD operation that fails in multiple betxn plugins leaves entry cache in inconsistent state
Closed: wontfix None Opened 8 years ago by nhosoi.

https://bugzilla.redhat.com/show_bug.cgi?id=1304682#c6

(In reply to thierry bordaz from comment #6)

There may be a bug in automember if we considere it should detect the
deletion of a group that is defined in one of its automembership
configuration.

The txn worked as expected on automember failure (be_txnpostop), the full
txn was aborted and the ADDed member (test5_auto) we removed from DB/Index.

A second bug is that it was not completely "undone" and apparently remained
in the entry cache. (a workaround for this bug would be a restart)


Any chance I can get a test case that does not require installing ipa?

I tried this on 1.3.5 and it worked as expected with no side effects:

[1] Setup automember plugin (generic config to catch all users)
[2] Create cn=group,dc=example,dc=com
[3] Add a user
[4] User is auto-added to group
[5] Delete group
[6] Add another user
[7] Add user fails with error 53 (as expected)
[8] Search for user, using the DN for the basedn, returns error 32 as expected

ldapsearch ... -b "uid=user,dc=example,dc=com"

If there are other required steps please provide them.

I also tried 1.3.4, and I setup the managed entry plugin: I still can not reproduce the issue.

Replying to [comment:6 mreynolds]:

I tried this on 1.3.5 and it worked as expected with no side effects:

[1] Setup automember plugin (generic config to catch all users)
[2] Create cn=group,dc=example,dc=com
[3] Add a user
[4] User is auto-added to group
[5] Delete group
[6] Add another user
[7] Add user fails with error 53 (as expected)
[8] Search for user, using the DN for the basedn, returns error 32 as expected

ldapsearch ... -b "uid=user,dc=example,dc=com"

If there are other required steps please provide them.

Hi Mark,

did you try
ldapsearch .... -b "uid=user2,dc=example,dc=com" -s base ?

or

ldapsearch .... -b "uid=user2,dc=example,dc=com" -s sub '(objectclass=*) ?

Replying to [comment:8 tbordaz]:

Replying to [comment:6 mreynolds]:

I tried this on 1.3.5 and it worked as expected with no side effects:

[1] Setup automember plugin (generic config to catch all users)
[2] Create cn=group,dc=example,dc=com
[3] Add a user
[4] User is auto-added to group
[5] Delete group
[6] Add another user
[7] Add user fails with error 53 (as expected)
[8] Search for user, using the DN for the basedn, returns error 32 as expected

ldapsearch ... -b "uid=user,dc=example,dc=com"

If there are other required steps please provide them.

Hi Mark,

did you try
ldapsearch .... -b "uid=user2,dc=example,dc=com" -s base ?

or

ldapsearch .... -b "uid=user2,dc=example,dc=com" -s sub '(objectclass=*) ?

Error 32 for both searches:

[root@ldap tickets]# ldapsearch -D cn=dm -W -xLLL -b "uid=user2,dc=example,dc=com" -s base objectclass=top
No such object (32)
Matched DN: dc=example,dc=com

[root@ldap tickets]# ldapsearch -D cn=dm -W -xLLL -b "uid=user2,dc=example,dc=com" -s sub objectclass=top
No such object (32)
Matched DN: dc=example,dc=com

8b34963..6e862f3 master -> master
commit 6e862f3
Author: Mark Reynolds mreynolds@redhat.com
Date: Wed Jun 22 14:17:59 2016 -0400

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

7 years ago

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/1787

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Log in to comment on this ticket.

Metadata