Bug 2113056 - Import may break replication because changelog starting csn may not be created
Summary: Import may break replication because changelog starting csn may not be created
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.9
Assignee: Pierre Rogier
QA Contact: RHDS QE
URL:
Whiteboard: sync-to-jira
: 1908553 1981334 (view as bug list)
Depends On: 2057056 2057058
Blocks: 2057059
TreeView+ depends on / blocked
 
Reported: 2022-08-01 19:49 UTC by mreynolds
Modified: 2023-07-04 16:36 UTC (History)
13 users (show)

Fixed In Version: 389-ds-base-1.3.10.2-17.el7_9
Doc Type: Bug Fix
Doc Text:
.Import from an LDIF file with replication metadata now works correctly Previously, importing an LDIF file with replication metadata could cause the replication to fail in certain cases: In the first case, a replication update vector (RUV) entry placed before the suffix entry in an imported LDIF file was ignored. As a consequence, the replication with the imported replica failed, because of a generation ID mismatch. This update ensures that Directory Server writes the skipped RUV entry at the end of the import. In the second case, a changelog reinitialized after an RUV mismatch did not contain the starting change sequence numbers (CSNs). As a consequence, the replication with the imported replica failed, because of a missing CSN in the changelog. This update ensures that Directory Server creates the RUV `maxcsn` entries, when reinitializing the changelog. As a result, with this update, administrators do not have to reinitialize the replication after importing from an LDIF file that contains replication metadata.
Clone Of: 2057058
Environment:
Last Closed: 2022-10-25 07:49:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker IDMDS-2412 0 None None None 2022-08-01 19:56:51 UTC
Red Hat Issue Tracker IDMDS-2548 0 None None None 2022-09-29 19:27:59 UTC
Red Hat Issue Tracker RHELPLAN-129839 0 None None None 2022-08-01 19:57:09 UTC
Red Hat Product Errata RHSA-2022:7087 0 None None None 2022-10-25 07:50:01 UTC

Comment 2 mreynolds 2022-08-01 19:51:21 UTC 
*** Bug 1908553 has been marked as a duplicate of this bug. ***
Comment 5 mreynolds 2022-10-12 15:45:32 UTC 
*** Bug 1981334 has been marked as a duplicate of this bug. ***
Comment 6 Akshay Adhikari 2022-10-20 15:50:33 UTC 
Build Tested: 389-ds-base-1.3.10.2-17.el7_9.x86_64

Steps:

1) Create a Supplier Consumer replication server.

2) Perform an Export operation on the Supplier.

3) Edit the ldif file and move the RUV as the first Entry.

4) Perform a re-import operation.

5) Restart the server, perform some updates/operations over the supplier, and check if replication is still working.

The replication is working, Marking it as VERIFIED.
Comment 10 errata-xmlrpc 2022-10-25 07:49:53 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 (Moderate: 389-ds-base security and bug fix update), 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-2022:7087
Note You need to log in before you can comment on or make changes to this bug.