Re: logsuccess FALSE vs. replica contextCSN

On Thu, Jun 16, 2022 at 12:42:46 +0200, Ondřej Kuzník wrote:

On Thu, Jun 16, 2022 at 12:28:27PM +0200, Geert Hendrickx wrote:

...

And thus update the contextCSN of their root DN (despite no other changes to the main db) - their contextCSN is now different than the provider's.

This obviously only happens with "logsuccess FALSE", but even in that case this should not be expected behaviour; refused updates should not change anything except getting logged to the accesslog?

This is with OpenLDAP 2.5.12 (migrating from 2.4.x)

Hi Geert, this sounds a lot like ITS#9641. Could you also check 2.6?

Thanks Ondřej, yes that ITS describes the same issue. I can still reproduce it with 2.6.2 as well as master.

Geert