Univention Bugzilla – Bug 33382
s4 role transfer fails
Last modified: 2013-11-19 06:41:33 CET
Created attachment 5630 [details] Do role transfer earlier in the script The s4 role transfer during backup2master fails. The current version checks for the old master object, which, at that point in the script, has already been deleted. Attached is a proposed patch which moves the role transfer ahead of the object deletion. Workaround on samba4 systems: Execute samba-tool fsmo seize --role=all --force after backup2master +++ This bug was initially created as a clone of Bug #26986 +++
In addition, while fixing this, the test when to execute the role transfer should be improved to check if samba4 is installed. Currently, it is only tested if samba-tool exists on the local system, but due to dependencies it is also available on systems with samba3. There, the call fails with an error due to a missing library.
Ok, role transfer is now done before deleting the old DC account from samba4, and only if sam.ldb exists locally.
OK: samba3 - backup2master OK: samba4 - backup2master Tests: backup2master, user creation, windows domain joins, additional slave domain join, user login with pre- and postbackup created users. OK: changelog Verified
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".