Univention Bugzilla – Bug 33732
Listener cache inhibits replication
Last modified: 2014-01-22 11:52:27 CET
+++ This bug was initially created as a clone of Bug #33731 +++
On a DC backup and a DC slave an inconsistency between ldap content and listener cache occurred. After calling univention-replicate-one the listener checked the upstream object against the listener cache and jumped to the next transaction because according to the cache the system was up-to-date:
11.12.13 15:29:05.335 LISTENER ( ALL ) : handler: replication considered
11.12.13 15:29:05.335 LISTENER ( INFO ) : handler: replication (up-to-date)
The listener should always pass the retrieved object to the replication module - no matter if the listener cache has already seen this object.
The exception for the replication module has already been implemented for errata 3.1-0 but it was ineffective due to a logic flaw.
I've added a test case to ucs-test for this issue: 10_ldap/48replication_listener_cache_up_to_date_check