Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 819643 - Database RUV could mismatch the one in changelog under the stress
Database RUV could mismatch the one in changelog under the stress
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.3
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Rich Megginson
IDM QE LIST
: Regression, TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-07 16:19 EDT by Rich Megginson
Modified: 2012-06-20 03:15 EDT (History)
6 users (show)

See Also:
Fixed In Version: 389-ds-base.1.2.10.2-14.el6
Doc Type: Bug Fix
Doc Text:
Cause: Renaming RDN to the same string sequence, in which only upper/lower cases are different in the replicated configuration. Consequence: The rename failed and the corresponding ruv element was untouched in the list. Fix: Allow renaming RDN to the same string with case difference, and make sure the failed ruv element is removed. Result: The heavy renaming operations work with no errors.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 03:15:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0813 normal SHIPPED_LIVE Low: 389-ds-base security, bug fix, and enhancement update 2012-06-19 15:29:15 EDT

  None (edit)
Description Rich Megginson 2012-05-07 16:19:22 EDT
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/359

Found in a stress test.

On one master (blademtv5), one RUV (against another master blademtv1) on database stopped being updated, on the other hand, RUV in the changelog keeps updated.  The mismatch stops the replication originated on blademtv1.

The cause was the simultaneous MODRDN operations caused conflicts and one conflict resolution failed, which left uncommitted CSN in the CSN list in the RUV element.  It prevented to get the max CSN to update the RUV on database.
Comment 1 Jenny Galipeau 2012-05-07 16:42:24 EDT
This issue was found executing reliability regression tests.  It is blocking QE from executing.
Comment 8 Rich Megginson 2012-05-18 18:07:05 EDT
commit d037c6b87607dabf766229bdaf57140a517599af
Author: Rich Megginson <rmeggins@redhat.com>
Date:   Fri May 18 15:49:11 2012 -0600
ssh://pkgs.devel.redhat.com/rpms/389-ds-base
Comment 10 Noriko Hosoi 2012-05-24 18:27:49 EDT
    Technical note added. If any revisions are required, please edit the
"Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content
Services team.

    New Contents:
Cause: Renaming RDN to the same string sequence, in which only upper/lower cases are different in the replicated configuration.
Consequence: The rename failed and the corresponding ruv element was untouched in the list.
Fix: Allow renaming RDN to the same string with case difference, and make sure the failed ruv element is removed.
Result: The heavy renaming operations work with no errors.
Comment 11 Noriko Hosoi 2012-05-24 20:29:08 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Renaming RDN to the same string sequence, in which only upper/lower cases are different in the replicated configuration.
Consequence: The rename failed and the corresponding ruv element was untouched in the list.
Fix: Allow renaming RDN to the same string with case difference, and make sure the failed ruv element is removed.
Result: The heavy renaming operations work with no errors.
Comment 12 Amita Sharma 2012-05-29 07:36:00 EDT
mmrepl mmraccept startup 	100% (2/2) 	  	 
mmrepl mmraccept run 	100% (23/23) 	  	 
mmrepl mmraccept cleanup 	100% (1/1)
Hence VERIFIED
Comment 13 errata-xmlrpc 2012-06-20 03:15:34 EDT
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/RHSA-2012-0813.html

Note You need to log in before you can comment on or make changes to this bug.