Bug 37049 - AD-Member setup (via system setup) drops joinscript error messages
AD-Member setup (via system setup) drops joinscript error messages
Product: UCS
Classification: Unclassified
Component: UMC - Setup wizard
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-0-errata
Assigned To: Arvid Requate
Stefan Gohmann
Depends on:
  Show dependency treegraph
Reported: 2014-11-26 14:17 CET by Arvid Requate
Modified: 2015-01-29 11:43 CET (History)
3 users (show)

See Also:
What kind of report is it?: ---
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:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, Usability
Max CVSS v3 score:

screenshot (74.98 KB, image/png)
2014-11-26 14:17 CET, Arvid Requate

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-11-26 14:17:18 CET
Created attachment 6475 [details]

Some logging information from admember.run_samba_join_script get's lost when an error occurs during AD-Member setup (initiated via system setup). The /var/log/univention/setup.log below shows the traceback, but looking at the python code one line before the exception there should be an error message and log output from running the joinscript:

        if p1.returncode != 0:
                ud.debug(ud.MODULE, ud.ERROR, "26univention-samba.inst failed with %d (%s)" % (p1.returncode, stderr))
                raise sambaJoinScriptFailed()

The setupl.log didn't capture this, and the error message in the UMC-Setup dialog is essentially empty  (the error message details are empty, see attached screeen shot):
__MSG__:Einrichten der Synchronisation von AD...
W: The config registry variable 'ldap/sasl/secprops/maxssf' does not exist
Create connector/ad/ldap/host
Create connector/ad/ldap/base
Create connector/ad/ldap/binddn
Create connector/ad/ldap/bindpw
Create connector/ad/ldap/kerberos
Setting connector/ad/mapping/syncmode
Setting connector/ad/mapping/user/ignorelist
Module: ad-certificate
Setting connector/ad/ldap/ssl
__MSG__:Umbennen bekannter SID-Objekte...
__MSG__:Ausführen des Samba Join-Skripts...
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/setup/setup_script.py", line 304,
 in run
    success = self.inner_run()
  File "/usr/lib/univention-system-setup/scripts/90_postjoin//10admember", line 108, in inner_run
    admember.run_samba_join_script(username, password)
  File "/usr/lib/pymodules/python2.7/univention/lib/admember.py", line 611, in run_samba_join_script
    raise sambaJoinScriptFailed()

run-parts: /usr/lib/univention-system-setup/scripts/90_postjoin//10admember exited with return code 1
=== 90_postjoin/20upgrade (2014-11-26 13:46:28) ===
Comment 1 Arvid Requate univentionstaff 2015-01-21 23:44:05 CET
Initialization of univention.debug was missing, at least in 90_postjoin/10admember

Fixed along with Bug #37481.
Comment 2 Stefan Gohmann univentionstaff 2015-01-22 07:08:00 CET

Tests: OK
Comment 3 Janek Walkenhorst univentionstaff 2015-01-29 11:43:47 CET