Univention Bugzilla – Bug 40417
Prevent update if DC Master has not been updated before (4.0)
Last modified: 2019-01-03 07:16:15 CET
Bug 37260 fixed this for the update to UCS 4.1, we should also fix this for UCS 4.0. The patch is an adjusted preup.sh, only one UCR variable would need to be adjusted, see attachment. +++ This bug was initially created as a clone of Bug #37260 +++ Currently it is possible to upgrade a DC Backup/Slave/Member to UCS 4.0 without upgrading the DC Master first. This is neither supported nor desirable and can lead to numerous errors. This is even worse since the "Release Updates" section of the Software Update module defaults to "UCS 4.0-0", even if there is still an update to e.g. 3.2-4 available. This way, updating to 4.0 can easily be achieved by accident. We should prevent this and show an appropriate dialog that says something like "Your domain controller master is still on version x.y-z, it is strongly recommended that the master domain controller is always the first system to be updated during a release update. Are you sure that you want to continue?" See also Ticket#2014120821000086 and http://forum.univention.de/viewtopic.php?f=48&t=3619
Created attachment 7401 [details] univention-updater-r64829.patch
There is a Customer ID set so I set the flag "Enterprise Customer affected".
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. 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.