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.
Created attachment 889093[details]
sssd and abrt logs
Description of problem:
When joined to domain in one part of the forest, segfaults are observed when querying users from a different tree in the forest. This users are still resolved.
Version-Release number of selected component (if applicable):
Using version:
sssd-1.11.2-65.el7
How reproducible:
intermittent
Steps to Reproduce:
Using our stock QE AD forest layout:
Primary: sssdad.com
Child: child1.sssdad.com
Second tree: sssdad_tree.com
testing phase ad_other_dc_01 joins the child domain under the root domain. This test phase checks to make sure users for the root domain and the child resolve.
The ad_other_dc_02 phase of the automation checks to make sure users for the second tree are resolved. The users properly resolve and this test phase happens at Wed Apr 23 16:07:12 EDT 2014 in the logs. A segfault is observed after this in dmesg and message log.
Apr 23 16:07:13 longdhcp-13-129-86 kernel: sssd_be[32229]: segfault at 0 ip 00007ffad03655e8 sp 00007fffd0c4b340 error 4 in libsss_ad.so[7ffad0339000+38000]
The phase ad_other_dc_03 joins the second tree domain and make sure users for the root domain and the second tree domain users resolve.
The ad_other_dc_04 phase of the automation checks to make sure users for the child domain resolve. These users properly resolve and this test phase happens at Wed Apr 23 16:07:45 EDT 2014 in the logs. A segfault is observed after this in dmesg and message log.
Apr 23 16:07:46 longdhcp-13-129-86 kernel: sssd_be[961]: segfault at 0 ip 00007fa6c62205e8 sp 00007fffdb2521f0 error 4 in libsss_ad.so[7fa6c61f4000+38000]
Attached the abrt and sssd debug logs.
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-0441.html
Created attachment 889093 [details] sssd and abrt logs Description of problem: When joined to domain in one part of the forest, segfaults are observed when querying users from a different tree in the forest. This users are still resolved. Version-Release number of selected component (if applicable): Using version: sssd-1.11.2-65.el7 How reproducible: intermittent Steps to Reproduce: Using our stock QE AD forest layout: Primary: sssdad.com Child: child1.sssdad.com Second tree: sssdad_tree.com testing phase ad_other_dc_01 joins the child domain under the root domain. This test phase checks to make sure users for the root domain and the child resolve. The ad_other_dc_02 phase of the automation checks to make sure users for the second tree are resolved. The users properly resolve and this test phase happens at Wed Apr 23 16:07:12 EDT 2014 in the logs. A segfault is observed after this in dmesg and message log. Apr 23 16:07:13 longdhcp-13-129-86 kernel: sssd_be[32229]: segfault at 0 ip 00007ffad03655e8 sp 00007fffd0c4b340 error 4 in libsss_ad.so[7ffad0339000+38000] The phase ad_other_dc_03 joins the second tree domain and make sure users for the root domain and the second tree domain users resolve. The ad_other_dc_04 phase of the automation checks to make sure users for the child domain resolve. These users properly resolve and this test phase happens at Wed Apr 23 16:07:45 EDT 2014 in the logs. A segfault is observed after this in dmesg and message log. Apr 23 16:07:46 longdhcp-13-129-86 kernel: sssd_be[961]: segfault at 0 ip 00007fa6c62205e8 sp 00007fffdb2521f0 error 4 in libsss_ad.so[7fa6c61f4000+38000] Attached the abrt and sssd debug logs.