Currently 54_smbtorture/05_samba_selftest fails in ucs 4.1-4 (Bug 42624), because there is a problem with shared libraries (rpath?) in the local build environement of that test. 54_smbtorture/01_smbtorture works though. No clue yet how to fix this: ===================================================================== root@master10:~# univention-install ucs-test-smbtorture root@master10:~# /usr/share/ucs-test/54_smbtorture/05_samba_selftest -f [...fails] root@master10:~# ldd /opt/samba-4.5.1/bin/samba | grep "not found" libcluster.so.0 => not found libcliauth.so.0 => not found libservice.so.0 => not found libprocess-model.so.0 => not found libevents.so.0 => not found libgensec.so.0 => not found libsamba-debug.so.0 => not found libMESSAGING.so.0 => not found libndr-samba4.so.0 => not found libsamba-modules.so.0 => not found ===================================================================== The is basically what fails: make testenv SELFTEST_TESTENV=ad_dc The test case was introduced to check a kernel issue, it would be good to see it working again.
Actually the smbtorture test result is invalid since some time, it's only that it shows now with samba 4.5.1 because the smbtorture perl code was improved. If I do the same test with UCS 4.1-3-errata 282 (samba 2:4.3.7-1.835.201607051) I see the same: ===================================================================== root@master10:~# ldd /opt/samba-4.3.7/bin/samba | grep "not found" libtevent-util-idle.so.0 => not found libcluster.so.0 => not found libldbsamba.so.0 => not found libcliauth.so.0 => not found libservice.so.0 => not found libauth4.so.0 => not found libntvfs.so.0 => not found libprocess-model.so.0 => not found libevents.so.0 => not found libsamba-debug.so.0 => not found libsamdb-common.so.0 => not found liberrors.so.0 => not found libMESSAGING.so.0 => not found libndr-samba4.so.0 => not found libsamba-modules.so.0 => not found =====================================================================
Patch disabled for the time being.
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
4.1 is OoM See Bug #49003 *** This bug has been marked as a duplicate of bug 49003 ***