allow all configuration changes online

389ds / 389-ds-base

The enterprise-class Open Source LDAP server for Linux

https://www.port389.org/

Other

213 stars 94 forks source link

allow all configuration changes online #2399

Open 389-ds-bot opened 4 years ago

389-ds-bot commented 4 years ago

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49340

Created at 2017-08-03 10:54:30 by lkrispen (@elkris)
Assigned to nobody

Issue Description

we have configuration options which are effective immediately, some which require restart and some which are totally rejected like:

dn: cn=changelog5,cn=config
changetype: modify 
add: nsslapd-encryptionalgorithm
nsslapd-encryptionalgorithm: AES

modifying entry "cn=changelog5,cn=config"
ldap_modify: Server is unwilling to perform (53)
additional info: Unwilling to apply nsslapd-encryptionalgorithm mods while the server is   running

we should accept these changes and turn them into "require restart"

389-ds-bot commented 4 years ago

Comment from firstyear (@Firstyear) at 2017-08-06 02:44:25

This is pretty specific. I think this needs to be managed on a case by case instance, because how we manage these values can change between modules / plugins...

389-ds-bot commented 4 years ago

Comment from firstyear (@Firstyear) at 2017-08-06 02:44:26

Metadata Update from @Firstyear:

Custom field component adjusted to None
Custom field origin adjusted to None
Custom field reviewstatus adjusted to None
Custom field type adjusted to None
Custom field version adjusted to None

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2017-08-10 17:18:08

Try cleanup all the UNWILLING-TO_PERFORM config updates, because this requires us to edit the dse.ldif (e.g. CI tests)

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2017-08-10 17:18:08

Metadata Update from @mreynolds389:

Issue set to the milestone: 1.3.7.0

389-ds-bot commented 4 years ago

Comment from firstyear (@Firstyear) at 2017-08-14 03:07:26

Yeah, that's why I said this should be done one at a time, because there are lots of places this could apply.

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:07:27

Metadata Update from @mreynolds389:

Issue set to the milestone: FUTURE (was: 1.3.7.0)

389-ds-bot commented 4 years ago

Comment from mreynolds (@mreynolds389) at 2020-05-06 16:06:43

Metadata Update from @mreynolds389:

Issue priority set to: normal
Issue set to the milestone: 1.4.5 (was: FUTURE)