Univention Bugzilla – Bug 38442
Not enough debug output in univention.lib.admember.py
Last modified: 2017-10-10 15:38:43 CEST
At Ticket#2015042721000385, I noticed that we do not log enough debug output in order to be able to really make use of log information for helping to trouble shoot systems that ran into AD problems while executing the setup wizard (e.g., during the credentials check or also in the join script) or the AD connection wizard. We really need more information here!
It currently blocks debugging for Bug #43885.
univention debug is now initialized. This at least generates some more output. See the following commits: 42a93e6a298016db3dec0236c6c69a691f4bd462 8ed88c886e93846f8a5c0d80795b1a679b8f0f4a bc954c5d85ec2253d87457b1dad4690226c1b90c
OK - code review OK - master ad member via UMC module, univention-samba install log in management-console-module-adconnector.log OK - slave ad member via univention-join, univention-samba install log in in join.log OK - jenkins tests OK - YAML
<http://errata.software-univention.de/ucs/4.2/192.html>