Univention Bugzilla – Bug 43117
Test case 00_checks/46_ntacl_sysvolcheck fails
Last modified: 2019-02-05 21:43:08 CET
The test case 46_ntacl_sysvolcheck fails in UCS@school multiserver environments, for example: http://jenkins.knut.univention.de:8080/job/UCSschool%204.1/job/UCSschool%204.1%20(R2)%20Multiserver/SambaVersion=s4-all-components/lastCompletedBuild/testReport/00_checks/46_ntacl_sysvolcheck/test/ (2016-12-05 05:28:10.338123) ERROR(<type 'exceptions.TypeError'>): uncaught exception - (61, 'No data available') (2016-12-05 05:28:10.338222) File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 176, in _run (2016-12-05 05:28:10.350320) return self.run(*args, **kwargs) (2016-12-05 05:28:10.350373) File "/usr/lib/python2.7/dist-packages/samba/netcmd/ntacl.py", line 270, in run (2016-12-05 05:28:10.358272) lp) (2016-12-05 05:28:10.358327) File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line 1732, in checksysvolacl (2016-12-05 05:28:10.383106) fsacl = getntacl(lp, dir_path, direct_db_access=direct_db_access, service=SYSVOL_SERVICE) (2016-12-05 05:28:10.383158) File "/usr/lib/python2.7/dist-packages/samba/ntacls.py", line 81, in getntacl (2016-12-05 05:28:10.391002) xattr.XATTR_NTACL_NAME) (2016-12-05 05:28:10.415777) error 2016-12-05 05:28:10 samba-tool ntacl sysvolcheck failed (2016-12-05 05:28:10.416561) error 2016-12-05 05:28:10 **************** Test failed above this line (110) ****************
r74991: * 00_checks/46_ntacl_sysvolcheck: Added more debug output (Bug #43117)
I've now disabled the test case in UCS@school environments: r75017: * 00_checks/46_ntacl_sysvolcheck: Disable test case in UCS@school environments (Bug #43117)
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018. Customers still on UCS 4.1 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.