Some operations are seen as NOOP that does not update the RUV, so replication can loop on it

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49466

• Created at 2017-11-24 10:59:44 by tbordaz (@tbordaz)
• Assigned to nobody

---

Issue Description

Some operation are considered as NOOP in urp (like DEL on a tombstone).
In such case the local RUV is not updated. This can lead to symptoms like https://pagure.io/389-ds-base/issue/49463

Received operation should update the RUV when they are processed. Even if the processing conclude it is a NOOP.

Package Version and Platform

NOOP have existed since at least since 1.3

Steps to reproduce

It can use the testcase of https://pagure.io/389-ds-base/issue/49463

Actual results

RUV is not updated on NOOP

Expected results

RUV should be update with NOOP

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-11-24 11:01:46

Metadata Update from @tbordaz:

• Custom field component adjusted to None
• Custom field origin adjusted to IPA
• Custom field reviewstatus adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-02-27 18:20:59

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.4.0

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-02-19 16:58:32

Metadata Update from @vashirov:

• Issue priority set to: normal
• Issue set to the milestone: 1.4.4 (was: 1.4.0)