Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1090653
Created attachment 889093
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
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Using our stock QE AD forest layout:
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: segfault at 0 ip
00007ffad03655e8 sp 00007fffd0c4b340 error 4 in
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: segfault at 0 ip
00007fa6c62205e8 sp 00007fffdb2521f0 error 4 in
Attached the abrt and sssd debug logs.
design_review: => 0
milestone: NEEDS_TRIAGE => SSSD 1.11.6
review: True => 0
testsupdated: => 0
owner: somebody => preichl
resolution: => fixed
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.11.6
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.