#47337 mep_pre_op: Unable to fetch origin entry
Closed: wontfix None Opened 9 years ago by rcritten.

During IPA automated testing I'm seeing some MEP errors logged in 389-ds. No IPA unit tests are failing so I don't know when we started seeing this.

I've seen this in F-19 and F-18.

For the purposes of this bug I reproduced in F-18

# rpm -q 389-ds-base

The IPA server is from master, it is the 3.2 beta 1 release.

To reproduce:

  • ipa-server-install ...
  • kinit admin
  • ipa hostgroup-add hg1 --desc=hg1
  • ipa hostgroup-add-member --hosts=hostname hg1
  • ipa hostgroup-del hg1

This shows up in the error log:

[19/Apr/2013:16:45:29 -0400] managed-entries-plugin - mep_pre_op: Unable to fetch origin entry "cn=hg1,cn=hostgroups,cn=accounts,dc=example,dc=com".

This is caused the referential integrity plugin doing the entry's membership cleanup. The "cleanup" triggers the the mep plugin, which tries to the find the origin entry, but it was already deleted. Fix is to move the error to the PLUGIN log level for internal operations.

git merge ticket47337
Updating 630c892..b4a4ef5
ldap/servers/plugins/mep/mep.c | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)

git push origin master
Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 1.12 KiB, done.
Total 7 (delta 4), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
630c892..b4a4ef5 master -> master

commit b4a4ef5

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.2 - 05/13 (May)

5 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/674

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)

2 years ago

Login to comment on this ticket.