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"
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...
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
Try cleanup all the UNWILLING-TO_PERFORM config updates, because this requires us to edit the dse.ldif (e.g. CI tests)
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.7.0
Yeah, that's why I said this should be done one at a time, because there are lots of places this could apply.
Metadata Update from @mreynolds: - Issue set to the milestone: FUTURE (was: 1.3.7.0)
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.5 (was: FUTURE)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2399
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)