Bug 1031226 - Convert ldbm_back_seq code to be transaction aware.
Summary: Convert ldbm_back_seq code to be transaction aware.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 23:23 UTC by Nathan Kinder
Modified: 2020-09-13 20:50 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.3.1.6-12.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:57:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 935 0 None None None 2020-09-13 20:50:42 UTC

Description Nathan Kinder 2013-11-15 23:23:36 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47598

The ldbm_back_seq code needs to be converted to be transaction aware.  We are seeing deadlock issues related to this code as described in the following FreeIPA ticket:

    https://fedorahosted.org/freeipa/ticket/3967
Comment 1 Sankar Ramalingam 2013-11-25 17:28:01 UTC 
Hi Mark, Can this be verified on DS side? If yes, can you add steps to reproduce?
Comment 2 mreynolds 2013-11-25 17:37:53 UTC 
Hi Sankar,

There are no steps to reproduce.  This was just make the function compliant with our backend transaction processes.
Comment 4 Milan Kubík 2014-02-17 09:51:32 UTC 
Sanity test/acceptance run against 389-ds-base-1.3.1.6-18.el7 doesn't seem to indicate regressions.

Marking verified as per Sankar's instructions.
Comment 5 Ludek Smid 2014-06-13 10:57:25 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.