Univention Bugzilla – Bug 35180
inconsistent behavior of " --keep-existing" (keep the SID) during samba4 join
Last modified: 2020-07-03 20:55:12 CEST
I have a s4 master and s4 slave, now i join the slave to the s4 domain. Then i rerun the samba4 join script, but the samba4 join fails (e.g. server not available). After the next samba4 join, my slave has a new SID. The problem is that, "--keep-existing" is set if the join script finds an account in the local sam.db. But during join the sam.db is deleted (cleanup_var_lib_samba), so after a failed join, "--keep-existing" is never used.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.