RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1542469 - Why does the mep_origination entry toggle from tombstone/not_tombstone?
Summary: Why does the mep_origination entry toggle from tombstone/not_tombstone?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 7.7
Assignee: thierry bordaz
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-06 12:11 UTC by Ming Davies
Modified: 2021-06-10 14:29 UTC (History)
11 users (show)

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
Clone Of:
Environment:
Last Closed: 2019-08-06 12:58:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2620 0 None None None 2020-09-13 22:07:55 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:58:42 UTC

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


Note You need to log in before you can comment on or make changes to this bug.