After update to UCS 4.4 Erratum 449: Problem with univention-directory-reports-cleanup

UCS - Univention Corporate Server
#1

After the update with UCM to erratum 449 i got the following email at midnight:

Traceback (most recent call last):
File “/usr/sbin/univention-directory-reports-cleanup”, line 46, in
for f in os.listdir(dirname): OSError: [Errno 2] No such file or directory: ‘/usr/share/univention-management-console-module-udm’

Heiko

Error in CRON job on a Kopano server
#2

I think there is an update regarding this issue:
https://errata.software-univention.de/ucs/4.4/350.html

EDIT: No this issue is still unsolved:

# /usr/sbin/univention-directory-reports-cleanup --help
Traceback (most recent call last):
  File "/usr/sbin/univention-directory-reports-cleanup", line 46, in <module>
    for f in os.listdir(dirname):
OSError: [Errno 2] No such file or directory: '/usr/share/univention-management-console-module-udm'
#3

Thank you for the report, it seems the error has been introduced with UCS 4.4 Erratum 346. I created an entry in our bug tracker: https://forge.univention.org/bugzilla/show_bug.cgi?id=50497

#4

same here - failed cron job (sinces yesterdays update to 4.4-2 errata350):

Traceback (most recent call last):
  File "/usr/sbin/univention-directory-reports-cleanup", line 46, in <module>
    for f in os.listdir(dirname):
OSError: [Errno 2] No such file or directory: '/usr/share/univention-management-console-module-udm'
#5

Issue is still unsolved but ticket status says “RESOLVED FIXED”.
Did I missed something?

#6

The status RESOLVED FIXED means a fix has been developed. The next step is that the fix has to be verified by a developer. If that is successful the status will change to VERIFIED FIXED. Once the fixed package has been released and can be installed on UCS systems, the last bug status will be CLOSED FIXED

#7

Okay. Thank you for clarification!

#8

Thanks for your fix.

Mastodon