This bug is created as a clone of upstream ticket:
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.
* 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".
is it possible to reproduce this outside of the IPA environment? If so, please provide verifications steps.
I can not reproduce the issue anymore. I removed the fix from the source and ran the IPA testcase, but the error did not appear. The fix was to just remove an unnessary error message from the errors log.
What appeared to previosuly cause the issue was:
 Enable mep plugin, and the referential integrity plugin
 Add a user
 Add a group, and add that user as a member of that group.
 Delete the user
 Check the errors logs for "Unable to fetch origin entry"
I can reproduce this issue in the IPA environment with the build without the fix using steps in the description:
[02/Jan/2015:23:48:11 +0100] managed-entries-plugin - mep_pre_op: Unable to fetch origin entry "cn=hg1,cn=hostgroups,cn=accounts,dc=example,dc=com".
With the build 389-ds-base-188.8.131.52-10.el7 there are no error messages related to mep_pre_op. Hence marking as VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.