Bug 1351447

Summary: Supplier can skip a failing update, although it should retry.
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: ekeck, gparente, mkolaja, nhosoi, nkinder, pbokoc, rmeggins
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.4.0-33.el7_2 Doc Type: Bug Fix
Doc Text:
If a replica update failed on the consumer side and was followed by another update that succeeded, the consumer's replication status was updated by the successful update, which caused the consumer to look like it was caught up. Consequently, the failed update was never retried, leading to data loss. With this update, a replication failure closes the connection and stops the replication session. This prevents further updates from changing the consumer's replication status, and allows the supplier to retry the failed operation in the next session, avoiding data loss.
Story Points: ---
Clone Of: 1310848 Environment:
Last Closed: 2016-08-02 18:37:46 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: 1310848    
Bug Blocks:    

Description Marcel Kolaja 2016-06-30 06:19:51 UTC
This bug has been copied from bug #1310848 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 5 Viktor Ashirov 2016-07-25 06:42:13 UTC
Build tested:
389-ds-base-1.3.4.0-33.el7_2

Reliability15 test was executed with replicas configured to use nsds5ReplicaReleaseTimeout: 60
Results: http://storm.idmqe.lab.eng.bos.redhat.com/qa/archive/ds/rhel72/reliab15/run4_1.3.4.0-33-convergence-fix/out/repl-monitor-output/

No issues found during the test. Convergence was achieved much sooner. Time lag was < 10 mins, compared to upto 5 hours with the default settings.

Marking as verified.

Comment 7 errata-xmlrpc 2016-08-02 18:37:46 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://rhn.redhat.com/errata/RHBA-2016-1544.html