Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1434335
Description of problem: This problem was fixed in: https://bugzilla.redhat.com/show_bug.cgi?id=1288229 many attrlist_replace errors in connection with cleanallruv but has re-appeared in this new version. I know it's harmless but it's preventing to read the logs and to find information. I have checked the patch in: https://pagure.io/389-ds-base/issue/48283 and it's included in the master branch. Version-Release number of selected component (if applicable): 389-ds-base-1.3.5.10-15.el7_3.x86_64 How reproducible: in lots of customers and even locally when there are invalid ruvs.
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1434335
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)
Metadata Update from @mreynolds: - Issue set to the milestone: FUTURE (was: 1.3.7 backlog)
here is my update from the bz for reference:
bug 1288229 fixed a real bug in managing nsds50ruv with many elements which could lead to invalid duplicate values and as a consequence to attrlist_replace errors for nsds50ruv attribute.
This bug is about nsslapd-referral and I think it is not a real bug, but a consequence of bad RUVs. I have not yet written a reproducer, but from my analysis I think this is what happens.
In a replication session the nsslapd-referrals in the mapping tree entry are updated based on the supplier ruv. The nsslapd-referral only uses the URL ignorig the replicaid If a ruv contains the same URL with different replicaids the generated list of referrals will contain duplicate urls and so lead to the attrlist_replace error.
Cleaning the RUV should prevent further occurrence of these messages.
But we could enhance the replication code to strip duplicate urls before updating the referrals, hiding problems with invalid ruvs
Metadata Update from @lkrispen: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field version adjusted to None
this is a test case to reproduce the attrlist_replace errors. it sets up 4 masters, removes 1 master and restores it with another replicaid without doing cleanallruv before
<img alt="ticket49180_test.py" src="/389-ds-base/issue/raw/files/8b7309fe473202bf5e02208d4759d9dcd2623a1c4fa4e7fe47ef8dc86e1cee13-ticket49180_test.py" />
Metadata Update from @lkrispen: - Issue set to the milestone: 0.0 NEEDS_TRIAGE (was: FUTURE)
<img alt="0001-Ticket-49180-errors-log-filled-with-attrlist_replace.patch" src="/389-ds-base/issue/raw/files/a6e92d6b1e93ab051bc1d8449154f411271f2668cd7d9b3ef1e3ba5d0c50afae-0001-Ticket-49180-errors-log-filled-with-attrlist_replace.patch" />
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to review (was: None)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
committed:
To ssh://git@pagure.io/389-ds-base.git 8fc58fd..6b1cbc8 master -> master
committed CI test: commit 83f04fe
committed to 1.3.7: commit 6e8ffe0
committed to 1.3.6: commit 6f585fa
Metadata Update from @lkrispen: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @vashirov: - Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)
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/2239
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.