Bug 1044138

Summary: mep_pre_op: Unable to fetch origin entry
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: mreynolds, nhosoi, rmeggins, vashirov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 389-ds-base- Doc Type: Bug Fix
Doc Text:
Cause: Deleting an entry while having the MEP and Referential Integrity plugin enabled Consequence: The MEP plugin tries to process the internal delete operation by the RI plugin, which logs a harmless error to the errors logs Fix: In the MEP plugin do log an error if the operation is internal Result: The errors log does not can any errors for successful operations that interact with MEP and RI plugins.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 09:29:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nathan Kinder 2013-12-17 21:17:31 UTC
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.

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".

Comment 2 Viktor Ashirov 2014-12-11 00:10:35 UTC

is it possible to reproduce this outside of the IPA environment? If so, please provide verifications steps.


Comment 3 mreynolds 2014-12-11 19:03:53 UTC
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:

[1]  Enable mep plugin, and the referential integrity plugin
[2]  Add a user
[3]  Add a group, and add that user as a member of that group.
[4]  Delete the user
[5]  Check the errors logs for "Unable to fetch origin entry"

Comment 4 Viktor Ashirov 2015-01-02 22:57:16 UTC
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- there are no error messages related to mep_pre_op. Hence marking as VERIFIED.

Comment 6 errata-xmlrpc 2015-03-05 09:29:49 UTC
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.