389-ds-base

#50526 Issue 50525 - nsslapd-defaultnamingcontext does not change when the assigned suffix got deleted
Closed by spichugi. Opened by mreynolds.
mreynolds/389-ds-base dsconf  into  master

Download 50526.patch

Bug Description:

If you delete the suffix that is set as the default naming context, the attribute
is not reset.

Also using dsconf to delete a nackend/suffix fails if there are vlv indexes, encrypted
attributes, or replication is configured.

Fix Description:

As for thedefault anming contetx, if there is a second suffix configured, it will be
automatically set as the new default naming context, otherwisethe attribute is not
modified.

For dsconf backend delete issue, it now checks and removes replication configuration
and agreements, and removes all the child entries under the backend entry.

relates: https://pagure.io/389-ds-base/issue/50525

I am thinking... Do we really need this part? If I understand correctly, we already set CONFIG_DEFAULT_NAMING_CONTEXT if LDAP_SUCCESS == rc.
Also the comment above states Removing while we were replacing.

Can we also add a case when we remove all of the backends? Just to check that nothing unexpected happens with nsslapd-defaultnamingcontext.
Here or to the basic testdirsrvtests/tests/suites/config/config_test.py::test_defaultnamingcontext...
Edited by spichugi

The commit message has a couple of typos...
nackend/suffix
thedefault anming contetx
otherwisethe

I am thinking... Do we really need this part? If I understand correctly, we already set CONFIG_DEFAULT_NAMING_CONTEXT if LDAP_SUCCESS == rc.

Yes we do, as this is what sets the in-memory value

Also the comment above states Removing while we were replacing.

I'll will correct his.

rebased onto 3055c6053d9452bb8bd6a38a65b33f3973bc9bbd

Changes applied, please review...

Removing word is still present in the comment...

The rest looks good to me! Ack

rebased onto fb3be041002931b94aa583646a170985783ae823

Pull-Request has been merged by mreynolds

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3582

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.