Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Deletion of attributes without a value on the master server now replicates correctly
Previously, when an attribute which does not have a value on the master server was deleted, the deletion was not replicated to other servers. The regression that caused this bug has been fixed and the change now replicates as expected.
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.
(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
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.
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