389-ds-base

#49561 MEP plugin, upon direct op failure, will delete twice the same managed entry
Closed: wontfix by tbordaz. Opened by tbordaz.

Closed: wontfix
Reopen Issue

Issue Description

All post-op are called even if one of them fails. So upon deletion of a managing entry MEP plugin will delete the managed entry.
Then post-op failure is detected, post-op are called again to process a kind of 'undo'. They are suppose to check the result of the operation (SLAPI_RESULT_CODE) to decide what they should do.

mep callbacks do not check the operation result and during the 'undo' phase delete again the managed entry (that is a tombstone at that time)

This is a minor issue as at the end of the day, the txn is aborted.
It does useless extra internal DEL and creates confusing logs

Package Version and Platform

All version

Steps to reproduce

To be done

Actual results

Enabling plugin-log level we can see
DEBUG - managed-entries-plugin - mep_del_post_op - Error retrieving pre-op entry cn=01960271-02-03-92-01,cn=groups,cn=accounts,dc=de,dc=pri,dc=o2,dc=com

Expected results

Should not see this msg

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.4

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

Metadata Update from @tbordaz:
- Custom field origin adjusted to IPA (was: None)

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

Metadata Update from @tbordaz:
- Issue set to the milestone: None (was: 1.3.4)

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

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.3.9 (was: 1.4.0)

d318d060f..c7da16fb3 master
4ab9bd595..906e093f5 389-ds-base-1.4.0
bcacbf24b..d0877d2a7 389-ds-base-1.3.9

Metadata Update from @tbordaz:
- 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/2620

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
None
None
None
None
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.