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.

Document URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Directory_Servers.html#s1-OpenLDAP

Section Number and Name: 
17.1.3. Configuring an OpenLDAP Server

Describe the issue: 
The very first sentence under the Table 17.5 says:
"Note that OpenLDAP no longer reads its configuration from the /etc/openldap/slapd.conf file."

This is not true. The slapd daemon reads from this file if there is no /etc/openldap/slapd.d directory (meaning that the newer and officially supported documentation format is not used; the old deprecated slapd.conf is used instead). If both are present, slapd.d configuration will be used.

Also, another sentence says:
"If you have an existing slapd.conf file from a previous installation, you can convert it to the new format by running the following command:"

I would add that this conversion is done automatically during updates when slapd.conf is found and slapd.d is not. When this conversion is done during an update, slapd.conf is renamed to slapd.conf.bak.

Suggestions for improvement: 
See above. Feel free to improve the wording;)

Thank you very much for taking the time to report this issue!