Bug 1542469

Summary:	Why does the mep_origination entry toggle from tombstone/not_tombstone?
Product:	Red Hat Enterprise Linux 7	Reporter:	Ming Davies <minyu>
Component:	389-ds-base	Assignee:	thierry bordaz <tbordaz>
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.4	CC:	bsmejkal, cpelland, lkrispen, mreynolds, nkinder, pasik, pvoborni, rcritten, rmeggins, tbordaz, tscherf
Target Milestone:	rc
Target Release:	7.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.9.1-3.el7	Doc Type:	If docs needed, set a value
Doc Text:	Cause: MEP post-op does not check if it is called during a failure. Consequence: It can try to delete twice the same managed entry resulting into strange error message. Fix: MEP post-op checks if it is called while the operation failed. In such case it returns immediately and does not try to delete a managed entry. Result: The error logs do not contain strange messages	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 12:58:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ming Davies 2018-02-06 12:11:03 UTC

Description of problem:
Customer is having problem deleting an IPA user.

Extract from the access log:
[17/Jan/2018:08:34:39.485811408 +0100] conn=65570 op=9 DEL dn="uid=xxxxxx,cn=users,cn=accounts,<base dn>"
[17/Jan/2018:08:34:39.504309656 +0100] conn=65570 op=9 RESULT err=1 tag=107 nentries=0 etime=0 csn=5a5f0510000000680000


Corresponding errors log:
[17/Jan/2018:08:34:39.493285360 +0100] - ERR - referint-plugin - _update_one_per_mod - Entry cn=ipausers,cn=groups,cn=accounts,<basedn>: deleting "member: uid=xxxxxxxx,cn=users,cn=accounts,<basedn>" failed (16)
[17/Jan/2018:08:34:39.496694706 +0100] - WARN - ldbm_back_delete - Attempt to Tombstone again a tombstone entry cn=<uid>,cn=groups,cn=accounts,<basedn>
[17/Jan/2018:08:34:39.500883701 +0100] - ERR - ldbm_back_delete - SLAPI_PLUGIN_BE_TXN_POST_DELETE_FN plugin returned error code but did not set SLAPI_RESULT_CODE


Version-Release number of selected component (if applicable):
ipa-server-4.5.0-22.el7_4.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
More details to follow

Comment 8 thierry bordaz 2019-03-18 13:55:33 UTC

Fixed upstream https://pagure.io/389-ds-base/issue/49561: POST

Comment 14 errata-xmlrpc 2019-08-06 12:58:23 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.

https://access.redhat.com/errata/RHBA-2019:2152