RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When enabling replication logging any successful update will log ::
[14/Feb/2018:07:49:42.035078104 -0500] - DEBUG - replication - multimaster_mmr_postop - error 0 for oparation 561.
[14/Feb/2018:07:49:42.036408086 -0500] - DEBUG - NSMMReplicationPlugin - replica_write_ruv - Failed to update RUV tombstone for dc=example,dc=com; LDAP error - 0

This can be misleading for customers

Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-18.el7.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Enable Replication logging
2. In replication, perform any operation for update
3. Check error logs for 
replica_write_ruv - Failed to update RUV tombstone for dc=example,dc=com; LDAP error - 0

One can execute - https://pagure.io/389-ds-base/issue/raw/files/a51cc3d9137740fe66aa5bb98ef78e38f8c7937d8d197cfb1cc86a1c2b23a1a5-0001-Ticket-49463-testcase.patch test case

Actual results:
replica_write_ruv - Failed to update RUV tombstone for dc=example,dc=com; LDAP error - 0

Expected results:
Error logs should be clean

Additional info:
Check upstream ticket - https://pagure.io/389-ds-base/issue/49460

*** This bug has been marked as a duplicate of bug 1551063 ***