When enabling replication logging any successful update will log
[21/Nov/2017:17:09:26.769484385 +0100] - DEBUG - NSMMReplicationPlugin - replica_write_ruv - Failed to update RUV tombstone for dc=example,dc=com; LDAP error - 0
It is side effect of https://pagure.io/389-ds-base/issue/48118 It applies to master and 1.3.7
attached testcase
Reports failure
Should not log error
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.7 backlog
<img alt="ticket49460.py" src="/389-ds-base/issue/raw/files/b47910c6bf2266a8e6c81a9b5ab8cf47fb60655d6a29dac92faed2b422ab9ec5-ticket49460.py" />
<img alt="0001-Ticket-49460-replica_write_ruv-log-a-failure-even-wh.patch" src="/389-ds-base/issue/raw/files/3c6ab736ebdd5017021263cc6e1d8caa26471667a10538eb285f18b51e22f880-0001-Ticket-49460-replica_write_ruv-log-a-failure-even-wh.patch" />
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review (was: None)
sorry for that
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to ack (was: review)
This looks pretty simple, so I'm okay to ack this. @lkrispen ?
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review (was: ack)
so why did you reset my ack ?
I didn't. I think I commented at the same time as you, and pagure reset it :(
Thanks for the review. Easy fix :)
git push origin master To ssh://git@pagure.io/389-ds-base.git 545b627..22a11d9 master -> master
git push origin 389-ds-base-1.3.7 To ssh://git@pagure.io/389-ds-base.git 4234a5f..bd23be0 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1551063
Issue linked to Bugzilla: Bug 1551063
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/2519
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.