Description of problem: In a replication (master-master or master-consumer) environment, when doing a dn: cn=user1,dc=ou,dc=o changetype: modify delete: any_attribute Or dn: cn=user1,dc=ou,dc=o changetype: modify replace: any_attribute on the master server, the attribute is deleted from the master but the attribute is not deleted on the replicated server (master or consumer). However, if I have dn: cn=user1,dc=ou,dc=o changetype: modify replace: any_attribute any_attribute: value Or dn: cn=user1,dc=ou,dc=o changetype: modify delete: any_attribute any_attribute: value the change is replicated to the consumer. Version-Release number of selected component (if applicable): 1.2.11.15-60.el6 There are no errors in the error log. Please provide a fix for this.
BTW, this issue doesn't exist on 1.2.11.15-50.el6.
Can I get an update on this please? Thank you.
(In reply to Thang Nguyen from comment #5) > Can I get an update on this please? Thank you. Fixed in upstream. Do you need a patch?
Hi Noriko, Thanks. Can you provide a patch? When will the fix be in Redhat repo?
(In reply to Thang Nguyen from comment #7) > Hi Noriko, > > Thanks. Can you provide a patch? When will the fix be in Redhat repo? Hello Thang, Can you see the attachment: #1060475? In terms of the release, we are working on it. Thanks for your patience, --noriko
Thanks Noriko! --thang
*** Bug 1254410 has been marked as a duplicate of this bug. ***
*** Bug 1254662 has been marked as a duplicate of this bug. ***
Steps to verify: 1. Set up MMR (hosts: Master1 and Master2) 2. delete an attribute without the value. ldapmodify -h Master1 ... << EOF dn: <DN> changetype: modify delete: <ATTR> EOF 3. check the attribute <ATTR> in Master2. If it is deleted, the fix is verified.
$ rpm -qa | grep 389-ds-base 389-ds-base-libs-1.2.11.15-74.el6.x86_64 389-ds-base-1.2.11.15-74.el6.x86_64 Verification steps: 1) Set up MMR: master1 - 389 master2 - 390 2) Add user entry to master1: $ ldapmodify -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 dn: uid=user,dc=example,dc=com changetype: add objectClass: top objectClass: person objectClass: inetUser uid: user sn: user cn: user description: test adding new entry "uid=user,dc=example,dc=com" 3) Check master2 for this entry: $ ldapsearch -h localhost -p 390 -D "cn=Directory Manager" -w Secret123 -b "uid=user,dc=example,dc=com" # user, example.com dn: uid=user,dc=example,dc=com objectClass: top objectClass: person objectClass: inetUser uid: user sn: user cn: user description: test 4) Delete attribute "description" from master1: $ ldapmodify -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 dn: uid=user,dc=example,dc=com changetype: modify delete: description modifying entry "uid=user,dc=example,dc=com" 5) Check master2 for this attribute: $ ldapsearch -h localhost -p 390 -D "cn=Directory Manager" -w Secret123 -b "uid=user,dc=example,dc=com" # user, example.com dn: uid=user,dc=example,dc=com objectClass: top objectClass: person objectClass: inetUser uid: user sn: user cn: user Marking as verified.
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-0737.html