Bug 1238790

Summary: ldapsearch on nsslapd-maxbersize returns 0 instead of current value
Product: Red Hat Enterprise Linux 7 Reporter: Viktor Ashirov <vashirov>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: amsharma, nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.4.0-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:42:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Viktor Ashirov 2015-07-02 15:56:02 UTC 
Description of problem:
ldapsearch on nsslapd-maxbersize returns 0

Version-Release number of selected component (if applicable):
389-ds-base-1.3.3.1-18.el7_1.x86_64

How reproducible:
always

Steps to Reproduce:
1. ldapsearch -LLL -D "cn=Directory Manager" -w Secret123 -b "cn=config" nsslapd-maxbersize | grep nsslapd-maxbersize

Actual results:
nsslapd-maxbersize: 0


Expected results:
nsslapd-maxbersize should report current value


Additional info:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_Reference/Core_Server_Configuration_Reference.html#cnconfig-nsslapd_maxbersize_Maximum_Message_Size

Zero 0 means that the default value should be used.
Comment 2 Noriko Hosoi 2015-07-02 21:41:36 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/48214
Comment 4 Amita Sharma 2015-07-13 09:47:08 UTC 
[root@dhcp201-167 /]# rpm -qa | grep 389
389-ds-base-libs-1.3.4.0-5.el7.x86_64
389-ds-base-1.3.4.0-5.el7.x86_64
389-ds-base-debuginfo-1.3.4.0-5.el7.x86_64

[root@dhcp201-167 /]# ldapsearch -LLL -D "cn=Directory Manager" -w Secret123 -b "cn=config" nsslapd-maxbersize | grep nsslapd-maxbersize
nsslapd-maxbersize: 2097152

Hence marking bug as VERIFIED
Comment 5 errata-xmlrpc 2015-11-19 11:42:50 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.

https://rhn.redhat.com/errata/RHBA-2015-2351.html