Description of problem:
The system to detect nested entry is broken for example, this direct update is assumed to be nested
[02/Oct/2020:12:48:42.407064204 +0000] conn=11 op=100 ADD dn="ipk11UniqueID=9a0baa52-04ad-11eb-a0dc-525400ea4c12,cn=keys,cn=sec,cn=dns,dc=ipa,dc=test"
[02/Oct/2020:12:48:42.504063075 +0000] conn=11 op=100 RESULT err=0 tag=105 nentries=0 wtime=0.000369948 optime=0.097011474 etime=0.097377063 csn=5f7721ab000800040000
[02/Oct/2020:12:48:42.427542634 +0000] - DEBUG - content-sync-plugin - sync_update_persist_betxn_pre_op - nested operation targets "ipk11UniqueID=9a0baa52-04ad-11eb-a0dc-525400ea4c12,cn=keys,cn=sec,cn=dns,dc=ipa,dc=test" (0x7fe7734bc800)
Also the way pending updates are flushed rely on betxn_preop - betxn_postop balance. Unfortunately some op seems to miss the postop, so operation remain pending
[02/Oct/2020:12:48:17.366968904 +0000] conn=28 op=1 MOD dn="cn=config"
[02/Oct/2020:12:48:17.374753804 +0000] conn=28 op=0 RESULT err=0 tag=97 nentries=0 wtime=0.009704399 optime=0.066472741 etime=0.076171658 dn="cn=directory manager"
[02/Oct/2020:12:48:17.392523825 +0000] - DEBUG - content-sync-plugin - sync_update_persist_betxn_pre_op - primary operation targets "cn=config" (0x7fe7734bc800)
#post op is not called
Version-Release number of selected component (if applicable):
regression introduced pagure ticket 51190
How reproducible:
TBD
At the moment detected with DNSSEC tests from freeipa
Actual results:
Direct updates are stated as nested (plugin log enabled)
Expected results:
Direct updates should be primary update.
Additional info:
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