In ticket 49516 the objectclass nsChangelogConfig was added to define the changelog5 entry instead of using extensibleObject. But the attribute nsslapd-encryptionalgorithm is missing.
This makes installations using this objectclass fail when trying to enable changelog encryption, eg: suites/replication/encryption_cl5_test.py
Double check 1.3.7/1.3.8 to see if it applies there
Metadata Update from @mreynolds: - 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 - Issue set to the milestone: 1.4.0
fixed in #49761, close as duplicate
Metadata Update from @lkrispen: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
@lkrispen, do you mind to describe which commit in #49761 fixed this ticket and how ?
https://pagure.io/389-ds-base/c/7b3c401a8fa914e8436e17dd46e8b7866759240b
It just adds the attributes to the changelogconfig objectclass
Indeed I did not find the commit into #49761 commits list. Thanks :)
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/2887
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: duplicate)
Login to comment on this ticket.