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:
Did "yum update" to update OpenLDAP server from RHEL 6.6 to RHEL 6.7 and after the update the OpenLDAP server was not working.

Version-Release number of selected component (if applicable):
Updating from:
RHEL 6.6, OpenLDAP 2.4.39

to:RHEL 6.7 and, OpenLDAP 2.4.40

How reproducible:
Always

Steps to Reproduce:
1. yum update on the OpenLDAP server with RHEL 6.6

Additional info:
My solution was to revert back the server to RHEL 6.6 and OpenLDAP 2.4.39.

It might be related to this:
https://bugzilla.redhat.com/show_bug.cgi?id=1160467

and a configuration problem on my end. I am using slapd.conf with:
TLSProtocolMin 3.1
TLSCipherSuite HIGH

Please let me know if you need further information.

If you require TLS1.1 to be used, your configuration should only set TLSProtocolMin:

TLSProtocolMin 3.2

See slapd-config(5), option olcTLSProtocolMin.

Thanks!

I will try that. However, just to let you know that I was following Red Hat resolution for POODLE vulnerability as explained here:
https://access.redhat.com/solutions/1234843

So slapd should still work properly after upgrading, is that right?

This bug should be resolved with resolving bug 1249092. Thus closing as NEXTRELEASE.