Univention Bugzilla – Bug 39290
ValidationError not handled by schoolwizards
Last modified: 2019-02-05 21:20:11 CET
We recevied the following traceback: Die Ausführung des Kommandos schoolwizards/classes/put schoolwizards/classes ist fehlgeschlagen: Traceback (most recent call last): File "%PY2.7%/univention/management/console/base.py", line 282, in execute function(self, request) File "%PY2.7%/ucsschool/lib/schoolldap.py", line 205, in wrapper_func return func( *args, **kwargs ) File "%PY2.7%/univention/management/console/modules/schoolwizards/__init__.py", line 121, in _decorated ret = func(self, request, *a, **kw) File "%PY2.7%/univention/management/console/modules/schoolwizards/__init__.py", line 218, in _modify_obj obj.modify(ldap_user_write, validate=False) File "%PY2.7%/ucsschool/lib/models/base.py", line 421, in modify success = self.modify_without_hooks(lo, validate, move_if_necessary) File "%PY2.7%/ucsschool/lib/models/group.py", line 183, in modify_without_hooks success = share.modify(lo) File "%PY2.7%/ucsschool/lib/models/base.py", line 421, in modify success = self.modify_without_hooks(lo, validate, move_if_necessary) File "%PY2.7%/ucsschool/lib/models/base.py", line 435, in modify_without_hooks raise ValidationError(self.errors.copy()) ValidationError: {'school_group': ['"Schulklasse" ist erforderlich. Bitte erg\xc3\xa4nzen Sie diese Information.']} Version: 4.0-2 errata263 (Walle)
Reported again, 4.0-3 errata302 (Walle)
*** Bug 36763 has been marked as a duplicate of this bug. ***
(In reply to Florian Best from comment #2) > *** Bug 36763 has been marked as a duplicate of this bug. *** See also Bug 36763 - a different error message but same problem / code path.
This issue has been filled against UCS@school 4.0. The maintenance with bug and security fixes for UCS@school 4.0 has ended on May 31, 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3 (or later). Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.