Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1574602
Description of problem: If we have a cascading replication scenario and we enable MemberOf plugin and the fractional replication, it breaks the replication after we add 'member' attribute to the group. Version-Release number of selected component (if applicable): 389-ds-base-1.3.7.5-18.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a topology with a master, a hub, and a consumer 2. Enable memberOf plugin in all instances, set memberofautoaddoc to 'memberOf', and restart 3. In the agreements, set nsDS5ReplicatedAttributeListTotal to '(objectclass=*) $ EXCLUDE ') and nsDS5ReplicatedAttributeList to '(objectclass=*) $ EXCLUDE memberOf 4. Add a user 5. Add a group 6. Test that the replication works 7. Add the user as a member of the group 8. Test that the replication works Actual results: replication fails with the next message in the error log. [03/May/2018:11:53:27.018990501 -0400] - INFO - NSMMReplicationPlugin - bind_and_check_pwp - agmt="cn=101" (qeos-60:39101): Replication bind with SIMPLE auth resumed [03/May/2018:11:53:27.027736321 -0400] - WARN - NSMMReplicationPlugin - repl5_inc_update_from_op_result - agmt="cn=101" (qeos-60:39101): Consumer failed to replay change (uniqueid 0e0f5602-4eea11e8-8673f23e-8486cb81, CSN 5aeb3061000000010000): Operations error (1). Will retry later. [03/May/2018:11:53:27.028465846 -0400] - WARN - NSMMReplicationPlugin - repl5_inc_update_from_op_result - agmt="cn=101" (qeos-60:39101): Consumer failed to replay change (uniqueid 0e0f5601-4eea11e8-8673f23e-8486cb81, CSN 5aeb3061000100010000): Operations error(1). Will retry later. [03/May/2018:11:53:27.122933027 -0400] - ERR - NSMMReplicationPlugin - release_replica - agmt="cn=101" (qeos-60:39101): Unable to send endReplication extended operation (Operations error) Expected results: replication should work without any errors. Additional info: we don't have the failure on 389-ds-base-1.3.7.5-11.el7.x86_64. It appears on 389-ds-base-1.3.7.5-12.el7.x86_64. So it is a regression. I found the bug while looking at bz1352121 test case failures. If we do the steps 2-3 on the master and the consumer only, the test passes. And the failure is still present on F28 389-ds-base built from master branch.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1574602
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Filed PR:
https://pagure.io/389-ds-base/pull-request/49672
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @spichugi: - Custom field reviewstatus adjusted to ack (was: review)
commit afb755b master
89a9de9..de9fb25 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
55cce82..9c2ec69 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
a8a94b3..05816f0 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue set to the milestone: 1.3.6.0 (was: 0.0 NEEDS_TRIAGE) - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2730
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.