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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/407

Running the multi_plugin test in valgrind:
==27981== 24 bytes in 1 blocks are definitely lost in loss record 248 of 1,456
==27981==    at 0x4A04A28: calloc (vg_replace_malloc.c:467)
==27981==    by 0x4C57EE9: slapi_ch_calloc (ch_malloc.c:243)
==27981==    by 0x4CA11AC: slapi_mods_new (modutil.c:93)
==27981==    by 0xB0FAE6B: dna_pre_op (dna.c:3254)
==27981==    by 0xB0FB08C: dna_mod_pre_op (dna.c:3334)
==27981==    by 0x4CB2228: plugin_call_func (plugin.c:1453)
==27981==    by 0x4CB20DB: plugin_call_list (plugin.c:1415)
==27981==    by 0x4CB066F: plugin_call_plugins (plugin.c:398)
==27981==    by 0xB577B8B: ldbm_back_modify (ldbm_modify.c:442)
==27981==    by 0x4C9E6B6: op_shared_modify (modify.c:945)
==27981==    by 0x4C9D8E2: modify_internal_pb (modify.c:616)
==27981==    by 0x4C9D45E: slapi_modify_internal_pb (modify.c:471)
==27981==    by 0x4CBF4F3: pw_mod_allowchange_aci (pw.c:1324)
==27981==    by 0x4291ED: pw_init (pw_mgmt.c:304)
==27981==    by 0x42150F: main (main.c:1217)

This will need to be verified by a developer by running valgrind when running the multi-plugin test.

QE verify sanity only, no regressions found with DNA and multi-plugin testing

I verified there is no memory leak observed with 389-ds-base-1.2.11.15-11.el6.x86_64.

Steps: 
Ran the multi_plugin as well as DNA test cases against the valgrind enabled 389-ds-base.
The valgrind output files do not include the memory leak reported by Nathan on 2012-07-23.
# egrep dna_ *.vg.*
#

Please change the status to VERIFIED.

Thanks Noriko.

DNA and multiplugin passed 100%
Hence marking bug as VERIFIED.

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-0503.html