Univention Bugzilla – Bug 43007
Pre-checks when (re)joining
Last modified: 2023-06-12 15:39:57 CEST
If Bug #43006 is implemented, UCS@school should check if the joining slave is suitable for the rest of the UCS@school environment (correct settings, compatible UCS@school version, ...). +++ This bug was initially created as a clone of Bug #43006 +++ Currently there is no possibility to perform some checks *before* the actual join process starts. Cause of this requirement: there are situations where the joining system wants to check the environment it is joining in, e.g. check if the master has a matching/compatible UCS/UCS@school version. Especially in case of a rejoin the pre-checks are important → when using an early join script (e.g. 00_aaaa.inst) the join process has already been started and changes have been made to LDAP and/or local system (changed password of machine account). It would be great if univention-join would perform pre-checks on the backup/slave/memberserver AND on the UCS master. So the slave is able to abort joining if the master/environment is not suitable and the master is also able to prevent the join if the slave is not suitable for joining. In UCS@school it would be possible to prevent (re)join attempts from outdated/incompatible UCS@school slaves.
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.