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.

Description of problem: Automated acceptance tests execution shows crashes from latest builds of 389-ds-base.

Version-Release number of selected component (if applicable): 389-ds-base-1.3.4.0-10

How reproducible: Consistently for 1.3.4.0-9 and 1.3.4.0-10.


Steps to Reproduce:
1. Run automated acceptance from Jenkins. Build a trigger job for RHEL72.
2. Wait till the acceptance reports are generated. Nearly 10 hrs.
3. Crash reports generated from the acceptance machine.

Actual results: Slapd crashes for replication tests.

Expected results: No crash

Additional info: This looks like its coming from NSS.

Created attachment 1061885 [details]
Stacktrace for slapd crash

The crash is coming from Distrib_logic tests. I ran it under valgrind to check what is the output. It will be available soon.

Created attachment 1062598 [details]
Valgrind output for Distrib_logic tests

Created attachment 1063002 [details]
Valgrind output with the scratch build

[root@mgmt2 ~]# rpm -qa |grep -i 389-ds-base
389-ds-base-libs-1.3.4.0-10.1.el7.x86_64
389-ds-base-1.3.4.0-10.1.el7.x86_64
389-ds-base-debuginfo-1.3.4.0-10.1.el7.x86_64

Upstream ticket:
https://fedorahosted.org/389/ticket/48250

No crashes observed with the latest build of 389-ds-base.
Acceptance test report - http://wiki.idm.lab.bos.redhat.com/qa/archive/beaker/x86_64/389-ds-base-1.3.4.0-11.el7.x86_64/Linux/20150817-223704.html

Also, no crashes observed with distrib_logic tests run on the same where I reproduced the crash for 389-ds-base-1.3.4.0-10.

Marking the bug as Verified based on the above statements.

Build tested:
[root@mgmt2 ~]# rpm -qa |grep -i 389
389-ds-base-1.3.4.0-11.el7.x86_64
389-ds-base-libs-1.3.4.0-11.el7.x86_64
389-ds-base-debuginfo-1.3.4.0-11.el7.x86_64

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.

https://rhn.redhat.com/errata/RHBA-2015-2351.html