Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 911467 - DNA plugin acceptance tests failed with "DB_LOCK_DEADLOCK" error.
DNA plugin acceptance tests failed with "DB_LOCK_DEADLOCK" error.
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.4
All Linux
urgent Severity high
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
: ZStream
Depends On: 907985
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-15 01:29 EST by Jiri Pallich
Modified: 2013-03-11 14:38 EDT (History)
10 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.11.15-12.el6_4
Doc Type: Bug Fix
Doc Text:
The DNA (distributed numeric assignment) plug-in, under certain conditions, could log error messages with the "DB_LOCK_DEADLOCK" error code when attempting to create an entry with an uidNumber attribute. Now, DNA handles this case properly and errors no longer occur during attempts to create entries with uidNumber attributes.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-11 14:38:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0628 normal SHIPPED_LIVE Moderate: 389-ds-base security and bug fix update 2013-03-11 18:35:12 EDT

  None (edit)
Description Jiri Pallich 2013-02-15 01:29:01 EST
This bug has been copied from bug #907985 and has been proposed
to be backported to 6.4 z-stream (EUS).
Comment 5 Sankar Ramalingam 2013-03-01 05:38:30 EST
Marking it as verified since there are no error messages observed after running DNA plugin tests from TET.
Comment 7 errata-xmlrpc 2013-03-11 14:38:42 EDT
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.

http://rhn.redhat.com/errata/RHSA-2013-0628.html

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