Bug 37260 - Prevent update if DC Master has not been updated before
Prevent update if DC Master has not been updated before
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Update - univention-updater
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1
Assigned To: Stefan Gohmann
Felix Botner
: interim-2
: 25825 39408 (view as bug list)
Depends on:
Blocks: 40417
  Show dependency treegraph
 
Reported: 2014-12-09 15:15 CET by Michael Grandjean
Modified: 2016-01-12 13:26 CET (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2014-12-09 15:15:38 CET
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
Comment 1 Nico Gulden univentionstaff 2015-09-28 10:35:16 CEST
*** Bug 39408 has been marked as a duplicate of this bug. ***
Comment 2 Nico Gulden univentionstaff 2015-09-28 10:36:22 CEST
The feedback in Bug #39408 suggest a way how the journey could be for the user.
Comment 3 Stefan Gohmann univentionstaff 2015-10-22 13:33:38 CEST
*** Bug 25825 has been marked as a duplicate of this bug. ***
Comment 4 Stefan Gohmann univentionstaff 2015-10-22 13:36:05 CEST
With UCS 4.1 we will configure automatic App release updates. Thus, we should add this check.
Comment 5 Stefan Gohmann univentionstaff 2015-10-24 20:59:58 CEST
The check has been added in the preup.sh script: r64829

Changelog: r64830
Comment 6 Felix Botner univentionstaff 2015-10-27 15:45:37 CET
OK 

root@slave-> univention-upgrade  --ignoressh --ignoreterm

Starting univention-upgrade. Current UCS version is 4.0-3 errata320

Checking for local repository:                          none
Checking for release updates:                           found: UCS 4.1-0

Do you want to update to 4.1-0 [Y|n]? y

Starting update to UCS version 4.1-0

...

Checking for space on /var/cache/apt/archives: OK
Checking for space on /boot: OK
Checking for space on /: OK
Checking for package status: OK
Checking LDAP schema: OK
WARNING: Your domain controller master is still on version 4.0-3.
         It is strongly recommended that the domain controller master is
         always the first system to be updated during a release update.
This check can be skipped by setting the UCR
variable update41/ignore_version to yes.
Error: Please check "/var/log/univention/updater.log" for details.
ERROR: update failed. Please check /var/log/univention/updater.log

OK - Changelog
Comment 7 Stefan Gohmann univentionstaff 2015-11-17 12:11:44 CET
UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".