Univention Bugzilla – Bug 37146
admember: check that univention-samba is installable
Last modified: 2019-02-21 20:29:24 CET
We should check that univention-samba is installable before attempting to configure the AD member mode. In my ucs-kt VM I had configured the AD DC as DNS server and had repository/online/server: univention-repository.knut.univention.de, which was not resolvable via the AD DNS.
Also, I guess we may want to commit the /etc/apt/sources.list.d/* after setting the nameserver in admember.py before checking in univention-samba is installable (or at least in case of failure), to avoid the case where the files are still empty.
For reference, this is the traceback I got:
02.12.14 12:33:07.546 MODULE ( PROCESS ) : Install univention-samba
02.12.14 12:33:07.547 MODULE ( WARN ) : univention-samba: Paket existiert nicht
02.12.14 12:33:11.559 MODULE ( PROCESS ) : Running samba join script
02.12.14 12:33:11.613 MODULE ( ERROR ) : Join process failed [OSError]: [Errno 2] Datei oder Verzeichnis nicht gefunden
02.12.14 12:33:11.614 MODULE ( ERROR ) : Traceback:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/univention/management/console/modules/adconnector/__init__.py", line 483, in admember_join
File "/usr/lib/pymodules/python2.7/univention/lib/admember.py", line 613, in run_samba_join_script
close_fds=True, env=my_env, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
OSError: [Errno 2] Datei oder Verzeichnis nicht gefunden
# ConfigurationError: Configuration error: host is unresolvable
Calling apt-get update would also be excellent.
Hit me, too.
This hit me again.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.
Customers still on UCS 4.0 are encouraged to update to UCS 4.3. 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.