Univention Bugzilla – Bug 53290
During upgrade to UCS 5.0: admindiary: ImportError: No module named client
Last modified: 2021-10-01 11:24:36 CEST
1 times in /var/log/univention/listener.log: https://jenkins.knut.univention.de:8181/job/UCS-5.0/job/UCS-5.0-0/job/AutotestUpgrade/SambaVersion=no-samba,Systemrolle=member/ws/test/listener.log Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/faillog.py", line 42, in <module> from univention.admin.handlers.users.user import unmapLocked File "/usr/lib/python2.7/dist-packages/univention/admin/handlers/__init__.py", line 62, in <module> from univention.admindiary.client import write_event ImportError: No module named client
My understand is: This Traceback occures only during upgrade and has no consequences for the system (all changes in LDAP are processed by the listener modules). Effort which needs to be spend for a fix is way higher than the benefit. -> WONTFIX Please reopen in case you disagree.
The effect is, that the faillog listener is not loaded during the upgrade. Transactions which happen during the upgrade are lost then but there shouldn't be any.
UCS 5.0 has been released: https://docs.software-univention.de/release-notes-5.0-0-en.html https://docs.software-univention.de/release-notes-5.0-0-de.html If this error occurs again, please use "Clone This Bug".
This now happens also in the UDM-Extensions and portal-groups listener during the upgrade to UCS 5.0: Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/udm_extension.py", line 45, in <module> import univention.admin.uldap as udm_uldap File "/usr/lib/python2.7/dist-packages/univention/admin/__init__.py", line 581, in <module> from univention.admin import modules, objects, syntax, hook, mapping # noqa File "/usr/lib/python2.7/dist-packages/univention/admin/modules.py", line 49, in <module> import univention.admin.handlers File "/usr/lib/python2.7/dist-packages/univention/admin/handlers/__init__.py", line 62, in <module> from univention.admindiary.client import write_event ImportError: No module named client Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/portal_groups.py", line 38, in <module> from univention.listener import ListenerModuleHandler, ListenerModuleConfiguration File "/usr/lib/python2.7/dist-packages/univention/listener/__init__.py", line 45, in <module> from univention.listener.handler import ListenerModuleHandler File "/usr/lib/python2.7/dist-packages/univention/listener/handler.py", line 36, in <module> from univention.admin.uldap import access, position File "/usr/lib/python2.7/dist-packages/univention/admin/__init__.py", line 581, in <module> from univention.admin import modules, objects, syntax, hook, mapping # noqa File "/usr/lib/python2.7/dist-packages/univention/admin/modules.py", line 49, in <module> import univention.admin.handlers File "/usr/lib/python2.7/dist-packages/univention/admin/handlers/__init__.py", line 62, in <module> from univention.admindiary.client import write_event ImportError: No module named client