Bug 1027496

Summary:	Replication Failures related to skipped entries due to cleaned rids
Product:	Red Hat Enterprise Linux 6	Reporter:	Rich Megginson <rmeggins>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	jgalipea, mkubik, nhosoi, nkinder
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-34.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1027502 (view as bug list)		Environment:
Last Closed:	2014-10-14 07:52:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1027502, 1061410

Description Rich Megginson 2013-11-06 23:28:49 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47585

I have a new issue that is affecting most of my systems since the upgrade to 389-ds-base-1.2.11.15-22.el6_4.x86_64.

My systems appear to have stopped replicating new changes with one another and with replication debugging turned up, it appears that they know about the changes they have pending, but they choose not to send any of them.

There don't appear to be any errors and any other signs of issue except for the fact that changes are not propagating.

Comment 1 Rich Megginson 2014-01-30 15:34:29 UTC

Once there is an official rhel 6.6 build with this fix, the svn commit r8202 should be merged into the tet rhel 6.6 branch

Comment 6 Milan Kubík 2014-07-22 13:06:04 UTC

After merging r8208 to RHEL66 branch, acceptance resulted in 100% PASS.

Architecture: i686, x86_64

DS version: 389-ds-base-1.2.11.15-38.el6

Comment 7 errata-xmlrpc 2014-10-14 07:52:03 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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html