Description Florian Best 2016-12-02 11:05:14 CET

There are various workarounds for settings/cn which is specified in all settings/- modules as superordinate-module.

(The (probably) only object of settings/cn is cn=univention,$ldap_base.)

All objects which reference settings/cn as superordinate don't give --superordinate as argument to the __init__ method, causing that it need special treatment:

management/univention-management-console-module-udm/umc/python/udm/__init__.py:
  1046 »   »   »   if superordinate and superordinate.module == 'settings/cn':
  1047 »   »   »   »   # false positive detected superordinate; Bug #32843
  1048 »   »   »   »   superordinate = None

management/univention-directory-manager-modules/modules/univention/admin/handlers/__init__.py:
   602 »   »   »   if superordinate_names == set(['settings/cn']):
   603 »   »   »   »   univention.debug.debug(univention.debug.ADMIN, univention.debug.WARN, 'No settings/cn superordinate was given.')
   604 »   »   »   »   return   # settings/cn might be misued as superordinate, don't risk currently

Either we should remove:
superordinate = 'settings/cn'
from all these modules (as it actually has no effect except that we need the workarounds from above)

Or we should adjust the __init__ of settings/cn.py:object to do something like:
if not superordinate:
    superordinate_dn = position.getDn() if position else lo.parentDn(dn)
    superordinate = univention.admin.objects.get('settings/cn', superordinate_dn)
super(object, self).__init__(..., superordinate=superordinate)