RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
During a DSE modify, be_preop callback are called. But be_postop callback are called at the condition dse_call_callback is different that SLAPI_DSE_CALLBACK_DO_NOT_APPLY.

This should systematically call be_postop if be_preop were called. In addition postop_modify_config_dse returning an invalid rc, systematically prevents DSE modify to call be_postop

Version-Release number of selected component (if applicable):

Since RHEL6 (introduce with https://fedorahosted.org/389/ticket/289)

How reproducible:
Easy to reproduce but not to detect.
To reproduce update any config attribute (ie. nsslapd-auditlog-logging-enabled).
To detect, I was using a debugger and put a breakpoint in 'dse_modify' at label 'done:'. Even on successful dse_call_callback, rc=0 and it does not enter in the block where postop are called.


Actual results:
be_post operation plugins are not call on any update of config attribute


Expected results:
If be_pre operation plugins are called then be_post op plugins should also be called 


Additional info:

This bug is not easy to verified. It breaks sync_repl that rely on a strict be_preop/be_postop balance. Even with sync_repl the verification requires a debug build (sync_repl) to add some traces.
other options to verify:
 - create a test be_preop/be_postop plugin that would check the balance
 - trace (gdb/stap) that be_postop/be_preop plugins are called
 - ???

Verified SanityOnly with rhpkg prep on stream-1.4-rhel-8.4.0 branch (389-ds-1.4-8040020210113163752.866effaa build)
Related commit : https://github.com/389ds/389-ds-base/commit/5ea53ebd765b68cef1f00d6cdd75e6d0b0bc39ca is present in the build
marking as verified:tested / SanityOnly

As per comment 4, moving to VERIFIED on build 389-ds-base-1.4.3.16-8.module+el8.4.0+9441+bd0f8b1f.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1835