Bug 38442 - Not enough debug output in univention.lib.admember.py
Not enough debug output in univention.lib.admember.py
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.2
Other Linux
: P5 normal with 1 vote (vote)
: UCS 4.2-2-errata
Assigned To: Stefan Gohmann
Felix Botner
Depends on:
  Show dependency treegraph
Reported: 2015-05-05 14:18 CEST by Alexander Kläser
Modified: 2017-10-10 15:38 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional): Error handling, External feedback, Troubleshooting, Usability
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2015-05-05 14:18: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!
Comment 1 Stefan Gohmann univentionstaff 2017-09-15 09:44:32 CEST
It currently blocks debugging for Bug #43885.
Comment 2 Stefan Gohmann univentionstaff 2017-10-02 17:05:59 CEST
univention debug is now initialized.  This at least generates some more output.

See the following commits:
Comment 3 Felix Botner univentionstaff 2017-10-04 13:22:54 CEST
OK - code review
OK - master ad member via UMC module, univention-samba install log in 
OK - slave ad member via univention-join, univention-samba install log in 
     in join.log
OK - jenkins tests 
Comment 4 Arvid Requate univentionstaff 2017-10-10 15:38:43 CEST