Univention Bugzilla – Bug 46535
S4-Connector deletes renamed group when the name has belonged to a just deleted group
Last modified: 2020-07-03 20:51:19 CEST
Maybe this is somehow related to Bug#18501 ============================================================ When a group (group_A) is deleted and another group (group_0) is renamed to that group (group_0 → group_A) pretty close after the deletion, both groups are gone. I tracked the source of that behavior down to the s4-connector and assume that it happened while the object is synchronized back to UCS/LDAP. When the gap between deletion and renaming is big enough, everything is fine. I assume in this case both transaction are handled in separate sync iterations. ----- debug:4 logs of the s4-connector.log as well as the listener.log are attached to the customers ticket. The Logs are from my testing environment.
Bug#18501 is about the AD-Connector and just backports the existing S4-Connector implementation for 33621#c7. I could imagine that this situation is the inverse of Bug 32263#c6 (and Bug 32263#c14) and we should simply check the entryUUID stored in the "UCS deleted" table against the present UCS object. I'll attach an untested idea for the patch.
Created attachment 9446 [details] 1.patch
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.