Bug 1546746

Summary:	replica_write_ruv log a failure even when it succeeds
Product:	Red Hat Enterprise Linux 7	Reporter:	Amita Sharma <amsharma>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED DUPLICATE	QA Contact:	Viktor Ashirov <vashirov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-19 15:48:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amita Sharma 2018-02-19 13:49:08 UTC

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

Comment 2 Nathan Kinder 2018-04-19 15:48:01 UTC


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