Univention Bugzilla – Bug 44428
Tracebacks are duplicated on UMC-Module initialization
Last modified: 2017-06-15 17:58:10 CEST
If an exception occurs during module initialization the traceback which is send to us is shown duplicated or even more than twice.
The generic error handling function is then also not called causing tracebacks instead of human readable error messages.
One liner fix.
r79129 | YAML Bug #44428
r79128 | Bug #44428: fix tracebacks during module initialization
Very fast way to reproduce this is opening the UDM module with this patch:
diff --git a/management/univention-management-console/src/univention/management/console/protocol/modserver.py b/management/univention-management-console/src/univention/management/console/protocol/modserver.py
index 8f6e7fb..523a59b 100644
@@ -269,7 +269,7 @@ def handle(self, msg):
» » » » elif key == 'credentials':
» » » » » self.__username = value['username']
» » » » » self.__user_dn = value['user_dn']
-» » » » » self.__password = value['password']
+» » » » » self.__password = value['password'] + '1'
» » » » » self.__auth_type = value.get('auth_type')
» » » » » self.__handler.username = self.__username
» » » » » self.__handler.user_dn = self.__user_dn
I replicated the behavior as described in Comment #3 and was able to reproduce it. I saw the same traceback multiple times in one error message.
When I upgraded univention-management-console I only saw one traceback per error message, but got multiple identical error messages.
(In reply to Richard Ulmer from comment #4)
> I replicated the behavior as described in Comment #3 and was able to
> reproduce it. I saw the same traceback multiple times in one error message.
> When I upgraded univention-management-console I only saw one traceback per
> error message, but got multiple identical error messages.
This is no regression compared to UCS 4.1 and happens because if you open e.g. the UDM module multiple requests are done. They are all failing and displayed accordingly. We might can fix this during cleanup of the error messages in Bug #38204 but not now.
@ Comment #5: Ok. -> Verified