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.
Description of problem:
Is it possible to modify the below error msg
Enable better logging for the error ldap_install_tls failed: [Connect error] [unknown error]
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
(In reply to Abhijit Roy from comment #0)
> Description of problem:
>
> Is it possible to modify the below error msg
>
> Enable better logging for the error ldap_install_tls failed: [Connect
> error] [unknown error]
Unfortunately, it's not really possible: error code is provided to SSSD by libopenldap, and libopenldap doesn't have much info besides underlying system call was interrupted.
But handling of this issue in general was improved greatly via bz 1920500
*** This bug has been marked as a duplicate of bug 1920500 ***
Apart from improving the handling of the issue I also improved the wording, even though it wasn't easy for the reasons mentioned by Alexey. With the fix you'll see the following sequence:
TLS handshake was interruped, provider will retry
...
ldap_install_tls failed: [Connect error]
Assuming TLS handshake was interrupted