with https://pagure.io/389-ds-base/issue/49562, the changelog is moved the main database. That means CLI will need to create changelog under the backend (instead of cn=changelog5) and that specific changelog tuning (directory/max/trim_interval/compact/encryption) need to be moved (to new changelog location) or abandoned (directory/compact).
To handle compatibility we should use ds_supports_new_changelog (lib389/utils).
1.4.4.4 and after
Use CLI (dsconf) to manage replication
Current CLI fails because looking at the wrong location
Make CLI able to use new CL location ( https://pagure.io/389-ds-base/issue/49562)
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue priority set to: critical - Issue set to the milestone: 1.4.4 - Issue tagged with: Replication, lmdb
PR https://pagure.io/389-ds-base/pull-request/51195
This PR should be applied on top of #49562 PR https://pagure.io/389-ds-base/pull-request/51181
Metadata Update from @tbordaz: - Issue tagged with: Documentation
Fix pushed upstream 0f1ab5f..bf6e486
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/4242
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 (was: fixed)
Login to comment on this ticket.