#50238 modrdn operation that fails in backend txn plugin can corrupt entry cache
Closed: wontfix by mreynolds. Opened by mreynolds.

Issue Description

I can only reproduce the issue in a IPA deployment, but if modrdn operation fails (via memberOf plugin failing) the original entry (before the modrdn attempt) is removed from the cache, and can no longer be updated.

The issue is that we replace the original cache entry with the new modrdn'ed entry, but if we fail in backend txn postop plugins we do not undo that swap.

Package Version and Platform

Steps to reproduce

1.
2.
3.

Actual results

Expected results


https://pagure.io/389-ds-base/pull-request/50239

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1680245

commit b30295a7b2e3d7cae47348a1df2f32adc5be7397

ea24c43a9..a06398439 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

70117f568..1bdf62751 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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 (was: fixed)

Metadata