Bug 1147479

Summary:	Memory leak during Reliab15 execution
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Kurik <jkurik>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.6	CC:	drieden, jgalipea, jkurik, jsvarova, nhosoi, nkinder, pm-eus, rmeggins, salmy, tlavigne, vashirov
Target Milestone:	rc	Keywords:	Regression, TestBlocker, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-47.el6	Doc Type:	Bug Fix
Doc Text:	Bug fixes for replication conflict resolution (BZ#1080185) introduced a memory leak bug, which increased the size of the Directory Server. With this update, the memory leak code has been fixed, and the size of the Directory Servers in the replication topology is now stable under the stress.	Story Points:	---
Clone Of:	1138745	Environment:
Last Closed:	2014-10-16 12:59:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1138745
Bug Blocks:

Description Jan Kurik 2014-09-29 10:38:58 UTC

This bug has been copied from bug #1138745 and has been proposed
to be backported to 6.6 z-stream (EUS).

Comment 7 Sankar Ramalingam 2014-10-07 07:23:46 UTC

Automated reliab15 execution revealed this memory leak issues. Hence, marking the bug with qe_test_coverage+ flag.

Comment 8 Viktor Ashirov 2014-10-07 09:55:59 UTC

Steps to verify manually with valgrind: https://bugzilla.redhat.com/show_bug.cgi?id=1138745#c23

Result: https://bugzilla.redhat.com/attachment.cgi?id=944320

With build 389-ds-base-1.2.11.15-47.el6 there is no mentions of ldbm_back_delete in valgrind log.  

Also, Reliab15 finished with good results (no memory leak), hence I mark this bug as VERIFIED.

Comment 10 errata-xmlrpc 2014-10-16 12:59:57 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.

http://rhn.redhat.com/errata/RHBA-2014-1623.html