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 830337 - usn + mmr = deletions are not replicated
Summary: usn + mmr = deletions are not replicated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-08 21:19 UTC by Nathan Kinder
Modified: 2020-09-13 20:12 UTC (History)
2 users (show)

Fixed In Version: 389-ds-base-1.2.11.12-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Configuring a directory server to use multi-master replication, and Entry USN, then deleting an entry from one of the masters. Consequence: The delete operation is not replicated to the other masters. Fix: Change Entry USN to not change the delete operation into a delete tombstone operation, and change it not to remove the operation before it can be logged in the changelog to replay to other servers. Result: An entry deletion operation is replicated to all servers when the server is configured to use Entry USN.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:17:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 383 0 None None None 2020-09-13 20:12:11 UTC
Red Hat Product Errata RHSA-2013:0503 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2013-02-21 08:18:44 UTC

Description Nathan Kinder 2012-06-08 21:19:00 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/383

I believe this is the root cause of https://fedorahosted.org/freeipa/ticket/2772

When you have 389 with usn and mmr enabled, and delete an entry, the delete operation is not changelogged and not replicated.

Comment 1 Jenny Severance 2012-06-19 16:55:35 UTC
see upstream tickets for information on reproducing/verifying

Comment 2 RHEL Program Management 2012-07-10 07:10:54 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-10 23:00:21 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 Jenny Severance 2012-08-28 13:32:09 UTC
automated regression test bug830337 in mmrepl/accept/accept.sh

Comment 6 Ján Rusnačko 2012-10-24 09:40:48 UTC
Steps to verify:

1) Setup two suppliers on ports $S1PORT and S2PORT

2) Enable USN plugin on both suppliers
ldapmodify -p $S1PORT -D "cn=directory manager" -w password << EOF
dn: cn=USN,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: on
EOF

ldapmodify -p $S1PORT -D "cn=directory manager" -w password << EOF
dn: cn=USN,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: on
EOF

3) Add user to supplier 1
ldapmodify -p $S1PORT -D "cn=directory manager" -w password -a << EOF
dn: uid=bug830337,o=Airius.com
cn: Bug 830337
sn: 830337
uid: bug830337
objectclass: top
objectclass: person
objectclass: organizationalperson
objectclass: inetorgperson
EOF

4) Check that user entry was propagated to supplier 2
ldapsearch -p $S2PORT -D "cn=directory manager" -w password -b "o=airius.com" "uid=bug830337" uid | grep -i "uid:" | awk '{print $2}'
bug830337

5) Check user`s USN on supplier 1:
ldapsearch -p $S1PORT -D "cn=directory manager" -w password -b "o=airius.com" "uid=$MYUID" entryusn | grep -i "entryusn" | awk '{print $2}'
0
 
6) Check user`s USN on supplier 2:
ldapsearch -p $S2PORT -D "cn=directory manager" -w password -b "o=airius.com" "uid=$MYUID" entryusn | grep -i "entryusn" | awk '{print $2}'
0

7) Delete user on supplier 2:
ldapmodify  -h localhost -p $S2PORT -D "cn=directory manager" -w password << EOF
dn: uid=bug830337,o=Airius.com
changetype: delete
EOF

8) Check that deletion has propagated to supplier 1:
ldapsearch -p $S1PORT -D "cn=directory manager" -w password -b "o=airius.com" "uid=bug830337" uid | grep -i "uid" 

echo $?
1

Verified

Comment 8 errata-xmlrpc 2013-02-21 08:17:30 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/RHSA-2013-0503.html


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