Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1498841 - Manpage incorrectly states ./ldaprc config file is used
Manpage incorrectly states ./ldaprc config file is used
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openldap (Show other bugs)
7.5
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Matus Honek
Patrik Kis
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-05 07:51 EDT by Matus Honek
Modified: 2018-04-10 14:16 EDT (History)
2 users (show)

See Also:
Fixed In Version: openldap-2.4.44-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 14:16:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0974 None None None 2018-04-10 14:16 EDT

  None (edit)
Description Matus Honek 2017-10-05 07:51:57 EDT
Description of problem:
Due to a patch from bug 38402, OpenLDAP clients do not make use of ldaprc configuration file placed in the current directory.

Version-Release number of selected component (if applicable):
Any RHEL-7.

How reproducible:
Always

Steps to Reproduce:
1. Set some option in an ldaprc file in the current directory.
2. Run a client (e.g. ldapsearch) from the very same directory.
3. See that the option is not taken into account at all.

Actual results:
Manpage states the ./ldaprc is used.

Expected results:
Manpage states the ./ldaprc is not used and that this diverges from usual (upstream) behaviour.

Additional info:
I believe it is unfortunate this change of behaviour got into downstream but in order not to introduce a regression rather manpage should be corrected instead of dropping the patch that causes the issue.
Comment 8 errata-xmlrpc 2018-04-10 14:16:19 EDT
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.

https://access.redhat.com/errata/RHEA-2018:0974

Note You need to log in before you can comment on or make changes to this bug.