#7341 nsslapd-sasl-max-buffer-size is hardcoded to '2097152' during install even if another value was provided in an LDIF ( --dirsrv-config-file )
Closed: fixed Opened by frenaud.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1527020

Description of problem:
# ipa-server-install --dirsrv-config-file params.ldif
with params.ldif:
~~~
dn: cn=config
changetype: modify
replace: nsslapd-maxsasliosize
nsslapd-maxsasliosize: 50000000
replace: nsslapd-sasl-max-buffer-size
nsslapd-sasl-max-buffer-size: 50000000
~~~
ends up with nsslapd-sasl-max-buffer-size at 2MB anyway due to:
https://bugzilla.redhat.com/show_bug.cgi?id=1044193
So during install the new value is correctly taken into account, but reset to
2M at the end:
~~~
2017-12-13T16:53:18Z DEBUG only: set nsslapd-sasl-max-buffer-size to '2097152',
current value [u'50000000']
2017-12-13T16:53:18Z DEBUG only: updated value [u'2097152']
~~~
The default value of 2MB is proving too low in some environments for initial
replication, so overriding it safely is a must.
Version-Release number of selected component (if applicable):
As of RHEL 7.4
How reproducible:
Always
Steps to Reproduce:
1. Install IPA server with "--dirsrv-config-file params.ldif" as above
2. Watch the log
Actual results:
~~~
2017-12-13T16:53:18Z DEBUG only: set nsslapd-sasl-max-buffer-size to '2097152',
current value [u'50000000']
2017-12-13T16:53:18Z DEBUG only: updated value [u'2097152']
~~~
Expected results:
Custom value is not overridden by hardcoded default value.
Additional info:
We should detect if the value was changed.
Known workaround:
* set the parameter nsslapd-sasl-max-buffer-size to 50000000 on the first IdM
server right after installation
* install all replica with ipa-replica-install --dirsrv-config-file params.ldif
* once installation is done, set the nsslapd-sasl-max-buffer-size to 50000000
in the replica as well.
As initial replication is done after the new value (50MB) is used, but before
the hardcoded value of 2MB is set, the parameter's value goes from:
dirserv default => 50MB => 2MB => 50MB

Metadata Update from @frenaud:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1527020

Metadata Update from @frenaud:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/1422

Metadata Update from @frenaud:
- Issue assigned to fcami

master:

  • 6f5042cd873a13cdae5ce41a6329a09dd7191da0 10-config.update: remove nsslapd-sasl-max-buffer-size override as https://pagure.io/389-ds-base/issue/47457 was fixed directly in 389 Directory Server.

Metadata Update from @frenaud:
- Issue set to the milestone: FreeIPA 4.5.5

ipa-4-6:

  • 2212fb57cfa367773bf2866255cbab80544f80ea 10-config.update: remove nsslapd-sasl-max-buffer-size override as https://pagure.io/389-ds-base/issue/47457 was fixed directly in 389 Directory Server.

ipa-4-5:

  • 8a0e7900daf5e8ddda4b7bb8e02eee99333eb841 10-config.update: remove nsslapd-sasl-max-buffer-size override as https://pagure.io/389-ds-base/issue/47457 was fixed directly in 389 Directory Server.

Metadata Update from @cheimes:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata