Univention Bugzilla – Bug 50277
Don't handle objects in ou=temporary_move_container_*
Last modified: 2021-03-17 08:52:49 CET
As can be seen in Bug #49876 comment 0: > noObject: uid=Xprdhkm2sxk,cn=q5x151o5zv,ou=temporary_move_container_1562854465.1,dc=AutoTest091,dc=local The S4-Connector modifies objects which are underneath of "ou=temporary_move_container_*" containers. This container is a temporary OU which exists for a short period during renaming containers. This is very error prone, as some changes probably don't get applied due to race conditions: 7: causes data lost. I think the S4-Connector should not touch currently being moved objects and wait until these objects are moved. Maybe the objects where only touched because they were detected as moved(?). My suggestion would be to not write 2 pickle files in the s4connector listener with the interim state (if new_dn or old_dn starts with ou=temporary_move_container_*). Instead this state should be detected and only one pickle file should be created after the new location is known. The S4-Connector should also know that there is currently a move (container rename) operation in progress and all changes which are done on Samba side should be delayed after the move operation succeeded.
I noticed a very similar behaviour in an environment, where the AD-Conenctor is used. There are always the same 3 or 4 users affected.
(In reply to Marc Schwarz from comment #1) > I noticed a very similar behaviour in an environment, where the AD-Conenctor > is used. There are always the same 3 or 4 users affected. It would probably be good if you describe this a little bit further, attach a ticket number, set the customer ID and Enterprise-Customer affected.
sorry, i wasn't able to get the logs in time; just made my note here first, so that I don't forget to attach them. I added customer-ID, there is no OTRS ticket yet. Logs will follow.