Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1551063

Summary: replica_write_ruv log a failure even when it succeeds
Product: Red Hat Enterprise Linux 7 Reporter: mreynolds
Component: 389-ds-baseAssignee: thierry bordaz <tbordaz>
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 7.4CC: amsharma, msauton, nkinder, rmeggins
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.8.2-1.el7 Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of:
: 1559464 (view as bug list) Environment:
Last Closed: 2018-10-30 10:13:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1559464    

Description mreynolds 2018-03-02 16:52:19 UTC 
This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/49460

#### Issue Description
When enabling replication logging any successful update will log

    [21/Nov/2017:17:09:26.769484385 +0100] - DEBUG - NSMMReplicationPlugin - replica_write_ruv - Failed to update RUV tombstone for dc=example,dc=com; LDAP error - 0


#### Package Version and Platform
It is side effect of https://pagure.io/389-ds-base/issue/48118
It applies to master and 1.3.7


#### Steps to reproduce

attached testcase

#### Actual results
Reports failure


#### Expected results
Should not log error
Comment 3 Nathan Kinder 2018-04-19 15:48:01 UTC 
*** Bug 1546746 has been marked as a duplicate of this bug. ***
Comment 5 Amita Sharma 2018-06-07 09:47:12 UTC 
[root@qeos-46 tickets]# pytest -s ticket49460_test.py 
================================================================ test session starts =================================================================
platform linux -- Python 3.6.3, pytest-3.6.1, py-1.5.3, pluggy-0.6.0
389-ds-base: 1.3.8.2-1.el7
nss: 3.34.0-4.el7
nspr: 4.17.0-1.el7
openldap: 2.4.44-13.el7
svrcore: 4.1.3-2.el7
FIPS: 0

rootdir: /export/tests/tickets, inifile:
plugins: metadata-1.7.0, html-1.19.0
collected 1 item                                                                                                                                     

ticket49460_test.py OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39001, 'ldap-secureport': 63701, 'server-id': 'master1', 'suffix': 'dc=example,dc=com'} was created.
OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39002, 'ldap-secureport': 63702, 'server-id': 'master2', 'suffix': 'dc=example,dc=com'} was created.
OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39003, 'ldap-secureport': 63703, 'server-id': 'master3', 'suffix': 'dc=example,dc=com'} was created.
INFO:lib389.topologies:Creating replication topology.
INFO:lib389.topologies:Joining master master2 to master1 ...
INFO:lib389.replica:SUCCESS: bootstrap to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 completed
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is was created
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is was created
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is working
INFO:lib389.replica:SUCCESS: joined master from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002
INFO:lib389.topologies:Joining master master3 to master1 ...
INFO:lib389.replica:SUCCESS: bootstrap to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 completed
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is was created
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is was created
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is working
INFO:lib389.replica:SUCCESS: joined master from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003
INFO:lib389.topologies:Ensuring master master1 to master2 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 already exists
INFO:lib389.topologies:Ensuring master master1 to master3 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 already exists
INFO:lib389.topologies:Ensuring master master2 to master1 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 already exists
INFO:lib389.topologies:Ensuring master master2 to master3 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is was created
INFO:lib389.topologies:Ensuring master master3 to master1 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 already exists
INFO:lib389.topologies:Ensuring master master3 to master2 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is was created
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user11,ou=people,dc=example,dc=com): 
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user21,ou=people,dc=example,dc=com): 
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user31,ou=people,dc=example,dc=com): 
.Instance slapd-master1 removed.
Instance slapd-master2 removed.
Instance slapd-master3 removed.


============================================================= 1 passed in 60.81 seconds ==============================================================
Comment 6 Amita Sharma 2018-06-07 09:47:30 UTC 
[root@qeos-46 tickets]# pytest -s ticket49460_test.py 
================================================================ test session starts =================================================================
platform linux -- Python 3.6.3, pytest-3.6.1, py-1.5.3, pluggy-0.6.0
389-ds-base: 1.3.8.2-1.el7
nss: 3.34.0-4.el7
nspr: 4.17.0-1.el7
openldap: 2.4.44-13.el7
svrcore: 4.1.3-2.el7
FIPS: 0

rootdir: /export/tests/tickets, inifile:
plugins: metadata-1.7.0, html-1.19.0
collected 1 item                                                                                                                                     

ticket49460_test.py OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39001, 'ldap-secureport': 63701, 'server-id': 'master1', 'suffix': 'dc=example,dc=com'} was created.
OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39002, 'ldap-secureport': 63702, 'server-id': 'master2', 'suffix': 'dc=example,dc=com'} was created.
OK group dirsrv exists
OK user dirsrv exists
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39003, 'ldap-secureport': 63703, 'server-id': 'master3', 'suffix': 'dc=example,dc=com'} was created.
INFO:lib389.topologies:Creating replication topology.
INFO:lib389.topologies:Joining master master2 to master1 ...
INFO:lib389.replica:SUCCESS: bootstrap to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 completed
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is was created
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is was created
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is working
INFO:lib389.replica:SUCCESS: joined master from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002
INFO:lib389.topologies:Joining master master3 to master1 ...
INFO:lib389.replica:SUCCESS: bootstrap to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 completed
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is was created
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is was created
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 is working
INFO:lib389.replica:SUCCESS: joined master from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003
INFO:lib389.topologies:Ensuring master master1 to master2 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 already exists
INFO:lib389.topologies:Ensuring master master1 to master3 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 already exists
INFO:lib389.topologies:Ensuring master master2 to master1 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 already exists
INFO:lib389.topologies:Ensuring master master2 to master3 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 is was created
INFO:lib389.topologies:Ensuring master master3 to master1 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39001 already exists
INFO:lib389.topologies:Ensuring master master3 to master2 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://qeos-46.lab.eng.rdu2.redhat.com:39003 to ldap://qeos-46.lab.eng.rdu2.redhat.com:39002 is was created
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user11,ou=people,dc=example,dc=com): 
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user21,ou=people,dc=example,dc=com): 
CRITICAL:tests.tickets.ticket49460_test:Adding user (cn=user31,ou=people,dc=example,dc=com): 
.Instance slapd-master1 removed.
Instance slapd-master2 removed.
Instance slapd-master3 removed.


============================================================= 1 passed in 60.81 seconds ==============================================================
Comment 8 errata-xmlrpc 2018-10-30 10:13:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3127