Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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/47592
automember_rebuild_task_thread() & automember_export_task_thread() do not destroy the search_pb pblocks.
Created attachment 862203[details]
valgrind output
Hi Mark,
I have enabled valgrind and executed auto member acceptance ( autoMemTask01() ),
Test case failed due to some issue of not able to stop the instance but it could successfully added the automember rebuild task -
add objectClass:
top
extensibleObject
add basedn:
ou=TaskEmployees,dc=autoMembers,dc=com
add filter:
(objectClass=posixAccount)
add scope:
sub
adding new entry cn=Rebuild,cn=automember rebuild membership,cn=tasks,cn=config
modify complete
Successfully added a task for running automembers Rebuild task
And I could see "automember" in the valgrind output. PFA.
Please guide if this is the issue?
(In reply to Amita Sharma from comment #5)
> Created attachment 862203[details]
> valgrind output
>
> Hi Mark,
>
> I have enabled valgrind and executed auto member acceptance (
> autoMemTask01() ),
> Test case failed due to some issue of not able to stop the instance but it
> could successfully added the automember rebuild task -
>
> add objectClass:
> top
> extensibleObject
> add basedn:
> ou=TaskEmployees,dc=autoMembers,dc=com
> add filter:
> (objectClass=posixAccount)
> add scope:
> sub
> adding new entry cn=Rebuild,cn=automember rebuild
> membership,cn=tasks,cn=config
> modify complete
>
> Successfully added a task for running automembers Rebuild task
>
> And I could see "automember" in the valgrind output. PFA.
> Please guide if this is the issue?
This is fine, the leak is fixed. You can mark this verified.
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.