389-ds-base

#50598 Ticket 50593 Investigate URP handling on standalone instance
Closed by spichugi. Opened by lkrispen.
lkrispen/389-ds-base t50593  into  master

Download 50598.patch

Bug: If the MMR plugin is enabled (on by default)
even if no replica was configured the MMR plugins were called
and eventually tried to generate cenotaphs for modrdn ops-

Fix: Check early if the operation affects a backend without replication
and return

The patch looks good. ACK

But I am missing something.
Does that mean that without that patch, any write operation on a standalone server was calling urp and write_changelog_and_ruv ?

I think so, but there are more checks for is_mmr_replica and I don't think it would have tried to write the changelog, for urp I think it only tried to do something since the conflict changes.

I hope we are safe now

rebased onto 0caae8aae062dc72f01dc9f0420cb05e85c3eb83

Pull-Request has been merged by lkrispen

Goods like a nice easy fix :) Thanks @lkrispen !

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/3654

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.