#49466 Some operations are seen as NOOP that does not update the RUV, so replication can loop on it
Opened 2 years ago by tbordaz. Modified 5 months ago

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


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

2 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

2 years ago

Metadata Update from @vashirov:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.0)

5 months ago

Login to comment on this ticket.

Metadata