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.

Bug 803937

Summary: sssd crashed after "LDAP connection error"
Product: Red Hat Enterprise Linux 6 Reporter: ksuzuoki
Component: sssdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: apeetham, grajaiya, jgalipea, jhrozek, prc
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: sssd-1.8.0-15.el6 Doc Type: Bug Fix
Doc Text:
Cause: when IPA client-side migration was performed, the SSSD used the start TLS operation on a connection that was already encrypted by GSSAPI Consequence: In some rare cases, especially when the TLS certificate was not available, this lead to sssd_be process crashing Fix: The migration procedure was fixed so that it spawns a new TLS-only connection for the migration Result: The client side password migration is more robust now
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 11:56:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Jenny Severance 2012-03-16 12:09:30 UTC
Please add steps to reproduce this crash

Comment 5 Jakub Hrozek 2012-03-16 16:27:47 UTC
(In reply to comment #4)
> Please add steps to reproduce this crash

We could never reliably reproduce the crash. There should only be sanity testing of the client-side migration.

The root cause seemed to be the fact that during migration, both TLS and GSSAPI were used at the same time and moreover, TLS was switched on by modifying a global option. We changed the way migration is performed to only use TLS for that single migration connection by passing a flag.

Sumit gave a very detailed overview of the problem along with the proposed solution in the opening comment of https://fedorahosted.org/sssd/ticket/924

Comment 6 Jenny Severance 2012-03-16 17:02:38 UTC
Verify sanity only - no regressions found

Comment 11 Jakub Hrozek 2012-04-03 18:49:33 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: when IPA client-side migration was performed, the SSSD used the start TLS operation on a connection that was already encrypted by GSSAPI

Consequence: In some rare cases, especially when the TLS certificate was not available, this lead to sssd_be process crashing

Fix: The migration procedure was fixed so that it spawns a new TLS-only connection for the migration

Result: The client side password migration is more robust now

Comment 12 Amith 2012-05-29 15:31:49 UTC
Verified on sssd-1.8.0-28.el6.
This bug has been verified sanity only and no related regressions detected.

Comment 14 errata-xmlrpc 2012-06-20 11:56:05 UTC
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/RHBA-2012-0747.html