Univention Bugzilla – Bug 37988
51_samba4.43access_sysvol.test fails in Jenkins
Last modified: 2019-02-05 21:20:44 CET
51_samba4.43access_sysvol.test fails in Jenkins: ERROR: Invalid IP address '127.0.0.1'! error 2015-03-03 06:00:00 TIMEOUT: Replication timout to local sam.ldb after 4197 seconds error 2015-03-03 06:00:00 **************** Test failed above this line (1) **************** http://jenkins.knut.univention.de:8080/job/UCSschool%204.0/job/UCSschool%204.0%20Multiserver/22/SambaVersion=s4-school-only-with-slave/testReport/51_samba4/43access_sysvol/test/ http://jenkins.knut.univention.de:8080/job/UCSschool%204.0/job/UCSschool%204.0%20Multiserver/21/SambaVersion=s4-school-only-with-slave/testReport/51_samba4/43access_sysvol/test/ Test is disabled with SKIP-UCSSCHOOL tag, please enable when this bug is fixed.
Failed again, but differently: S3-Master UCS-3.2-6 <http://jenkins.knut.univention.de:8080/job/UCS-3.2/job/UCS-3.2-6/job/Autotest%20MultiEnv/SambaVersion=s4,Systemrolle=master/67/testReport/junit/51_samba4/43access_sysvol/test/> ----create User Object created: uid=tkuwwjrn,cn=users,dc=autotest091,dc=local ----Put a file on sysvol as Administrator Domain=[AUTOTEST091] OS=[Unix] Server=[Samba 4.1.0-Debian] putting file /etc/hosts as \autotest091.local/t1 (4,7 kb/s) (average 4,7 kb/s) Waiting for replication: OK: replication complete (nid=9489 lid=9489) Done: replication complete. DRS replication took 0 seconds ----Access the folder Policies on sysvol as a user session setup failed: NT_STATUS_LOGON_FAILURE ----Put a file in the folder Policies on sysvol as a user ----Replace GPT.ini of the default domain policies as a user ----Remove GPT.ini of the default domain policies as a user ----Put a file in the Machine folder of the default domain policies as a user ----Check that the file ownership of the default domain policy is okay Object removed: uid=tkuwwjrn,cn=users,dc=autotest091,dc=local
This issue has been filled against UCS@school 4.0. The maintenance with bug and security fixes for UCS@school 4.0 has ended on May 31, 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3 (or later). 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.