User Report schlägt fehl

Hallo,

vielleicht betrifft es ja auch jemanden anders:
Wir haben bei einem Kunden folgenden Stacktrace wenn er einen Report erstellen will:

Interner Server-Fehler in "udm/reports/create (users/user)".
AttributeError: 'NoneType' object has no attribute 'info'
if token.attrs['name'] in base.info:
File "/usr/lib/pymodules/python2.7/univention/directory/reports/interpreter.py", line 163, in attribute
self.attribute(token, base_objects[0])
File "/usr/lib/pymodules/python2.7/univention/directory/reports/interpreter.py", line 95, in run
self.run(token, token.objects)
File "/usr/lib/pymodules/python2.7/univention/directory/reports/interpreter.py", line 80, in run
interpret.run()
File "/usr/lib/pymodules/python2.7/univention/directory/reports/document.py", line 128, in create_source
tmpfile = doc.create_source(objects)
File "/usr/lib/pymodules/python2.7/univention/directory/reports/report.py", line 69, in create
report_file = report.create(request.flavor, request.options['report'], request.options['objects'])
File "/usr/lib/pymodules/python2.7/univention/management/console/modules/udm/__init__.py", line 617, in _thread
result = func(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/univention/management/console/ldap.py", line 143, in _decorated
return method(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/univention/management/console/modules/udm/udm_ldap.py", line 82, in _decorated
return self._function( *tmp, **self._kwargs )
File "/usr/lib/pymodules/python2.7/notifier/__init__.py", line 104, in __call__
tmp = self._function()
File "/usr/lib/pymodules/python2.7/notifier/threads.py", line 82, in _run
Traceback (most recent call last):

Wir haben das Problem soweit eingegrenzt, dass es an einem fehlerhaften Vorgestezten liegt, und dazu: . https://forge.univention.org/bugzilla/show_bug.cgi?id=47149 geöffnet.

Gruß
Sven

still getting this issue after updating a server today to 4.4-0.
Then checked https://forge.univention.org/bugzilla/show_bug.cgi?id=47922

Is it correct to say that the fix will be applied/deployed in the next (first) 4.4 errata?

The corresponding errata has just been released.

Mastodon