Univention Bugzilla – Bug 49234
Check if container is moveable before moving to prevent reverting
Last modified: 2019-07-31 13:58:37 CEST
When UDM moves subtrees it fails and reverts all changes if there is one object underneath of the to be moved container which can't be identified as UDM module. This is e.g. the case for: ( WARN ) : Could not identify LDAP object 'cn=default,cn=ppolicy,cn=univention,dc=dev,dc=local' ( WARN ) : Could not identify LDAP object 'cn=backup,dc=dev,dc=local' etc. But the move starts, fails and reverts everything back. We should check for the objects being identifyable before starting any move, so that in an error case we wouldn't need to revert anything.
Moving containers has been delayed until all sub-objects are checked to be moveable. univention-directory-manager-modules (14.0.13-2) 5c236833b77f | Bug #49234: check if container content is moveable univention-directory-manager-modules.yaml 5c236833b77f | Bug #49234: check if container content is moveable
What I tested: Moved container with movable subobjects -> OK Moved container with nonmovable subobjects -> Error -> OK Jenkins -> OK Small yaml change: [4.4-1 9c917859fa] Bug #49234: YAML -> Verified
<http://errata.software-univention.de/ucs/4.4/205.html>