389-ds-base

#49466 Some operations are seen as NOOP that does not update the RUV, so replication can loop on it
Closed: wontfix by spichugi. Opened by tbordaz.

Closed: wontfix
Reopen Issue

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

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

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

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/2525

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
None
IPA
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.