389-ds will integrate changelog into main database:
It also changes the location of the configuration from a single entry cn=changelog5,cn=config to an entry for each backend in cn=changelog,<backend>,cn=ldbm database,cn=plugins,cn=config
With PR#51181 the entry cn=changelog5,cn=config no longer exists, its creation fails with UNWILLING_TO_PERFORM.
This breaks IPA in a few places, in particular:
Here the expected failure is err=68, it would be trivial to add err=53. A better way would be to reuse lib389 for setting up changelog, not sure how much refactoring that would involve.
Since the entry no longer exists, log message would be affected.
nsslapd-changelogmaxage now needs to be set for each backend.
There are possibly other places, but this is what came up first by searching for changelog5.
I have a potential fix for these issues, will submit a PR.
Created a new PR to handle both replication changelog locations:
Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)
to comment on this ticket.