Univention Bugzilla – Bug 37333
/usr/lib/univention-system-setup/scripts/90_postjoin//10admember exited with return code 1
Last modified: 2016-08-09 15:26:05 CEST
Created attachment 6529 [details] autotest-228-admember-w2k12-german-other-join-user.log From Jenkins tests: ------------------------------------------------------------------------------- __MSG__:Renaming well known SID objects... __ERR__:[Errno 2] No such file or directory 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 103, in inner_run admember.rename_well_known_sid_objects(username, password) File "/usr/lib/pymodules/python2.7/univention/lib/admember.py", line 848, in rename_well_known_sid_objects close_fds=True) File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory run-parts: /usr/lib/univention-system-setup/scripts/90_postjoin//10admember exited with return code 1 ------------------------------------------------------------------------------- <http://jenkins.knut.univention.de:8080/job/UCS-4.0/job/UCS-4.0-0/job/AD%20Member%20MultiEnv/Mode=installation,Version=w2k12-german-other-join-user/8/>
Looks like univention-ad-connector has not been installed. This could be fixed for ucs-test by specifying univention-ad-connector in the test dependencies. IMHO the USS script for AD Member setup should take care on a DC Master that this gets installed (just like it installs univention-samba by running univention.lib.admember.remove_install_univention_samba).
(In reply to Arvid Requate from comment #1) > Looks like univention-ad-connector has not been installed. > > This could be fixed for ucs-test by specifying univention-ad-connector in > the test dependencies. No, it is not the result of the test cases. It is a problem of the setup.
At Bug 40046, comment 16, we observed the same error. Is that critical? In this scenario we were testing an AD join with a new UCS appliance being re-joined (as the appliance had been pre-joined to allow a fast setup process option). > Created attachment 7687 [details] > setup.log: failed ad join > > AD Join fails in 90_postjoin/10admember with the following traceback, > setup.log is attached: > 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 111, in inner_run > admember.rename_well_known_sid_objects(username, password) > File "/usr/lib/pymodules/python2.7/univention/lib/admember.py", line 865, > in rename_well_known_sid_objects > close_fds=True) > File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ > errread, errwrite) > File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child > raise child_exception > OSError: [Errno 2] No such file or directory
> OSError: [Errno 2] No such file or directory Something getting run at that point is not present. The method rename_well_known_sid_objects calls well-known-sid-object-rename, which is part of univention-ad-connector. So it's fair to assume that Comment 1 applies. > Is that critical? Depends, if univention-ad-connector had been installed explicitly then this suggests that it has been removed, which could be considered critical. Otherwise probably not.
Ok, as discussed with Alex, this is not a ucs-test case issue but one of the system setup software selection: /usr/lib/univention-system-setup/scripts/90_postjoin/10admember is part of univention-system-setup and runs into this problem if "ad/member" is enabled *and* the AD-Connector has not been installed. Probably system-setup should automatically select the AD-connector component (and make it so that the user cannot de-select it in the software selection dialogue.
Has to be fixed, or app appliances wont be able to join as AD member, setting milestone to 4.1-3 errata
If it happens now always, we should fix it as 4.1-2-errata.
Checking with UCS 4.1-3.
I removed the code in the UMC frontend that auto selects the adconnector component. Instead, univention-ad-connector is added on the backend side. This should be more robust in any case. univention-system-setup (9.0.4-34): r71439 | Bug #37333: auto-install univention-ad-connector for AD member mode
OK: u-ad-connector gets installed for AD join even if the package is unchecked on the software page Reopen: changelog missing
(In reply to Erik Damrose from comment #10) > OK: u-ad-connector gets installed for AD join even if the package is > unchecked on the software page > Reopen: changelog missing True :) ... fixed. r71463 | Bug #37333: added changelog entry
Thanks, Verified :)
*** Bug 39371 has been marked as a duplicate of this bug. ***
UCS 4.1-3 has been released: https://docs.software-univention.de/release-notes-4.1-3-en.html https://docs.software-univention.de/release-notes-4.1-3-de.html If this error occurs again, please use "Clone This Bug".