Univention Bugzilla – Bug 39618
Improve release update policy
Last modified: 2020-08-28 14:17:28 CEST
The release update policy should be improved: - It should be possible to define which updates should be installed - Only Errata Updates + Patchlevel Releases + Minor Releaes + Major Releases - Should App Updates be automatically updated The problem is, that we need backward compatibility. So, we can't simply change the meaning of the current values.
While fixing this, we should adjust the default docker maintenance policies and activate Errata and Patchlevel releases only.
At least the syntax should be changed in UMC, as otherwise the UCS updater fails with an error message like # univention-upgrade --updateto=4.2 Checking for release updates: An error occurred - see "/var/log/univention/updater.log" for details # tail -14 /var/log/univention/updater.log Checking for release updates: Traceback in univention-upgrade: Traceback (most recent call last): File "/usr/sbin/univention-upgrade", line 434, in do_update update_available = performUpdate(options, checkForUpdates=options.check, silent=False) File "/usr/sbin/univention-upgrade", line 138, in performUpdate if func(options, checkForUpdates, silent): File "/usr/sbin/univention-upgrade", line 154, in do_release_update if options.updateto and UCS_Version(options.updateto) < UCS_Version(version_next): File "/usr/lib/pymodules/python2.7/univention/updater/ucs_version.py", line 61, in __init__ self.set(version) File "/usr/lib/pymodules/python2.7/univention/updater/ucs_version.py", line 94, in set raise ValueError('string does not match UCS version pattern') ValueError: string does not match UCS version pattern
(In reply to Philipp Hahn from comment #2) > At least the syntax should be changed in UMC spelling correction: changed → checked syntax.py: UCSVersion
There is a Customer ID set so I set the flag "Enterprise Customer affected".
+1 for App Updates from two school customers.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 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.
This is a major problem for one customer, which has 100 UCS-Servers with 500 Linux/Windows-VMs. The hosts are a mix of UCS-4.2, 4.3, 4.4. They must be configured to automatically install only errata updates (of their MA.MI-PL release). Release updates are installed when the maintenance window permits and when all VMs are migrated to other hosts only, so they MUST NOT be installed automatically. The hosts are all in one LDAP container, so only one maintenance policy can be applied. The work-around is to have 3 policies for the different UCS M.M-releases and to attach those policies to individual hosts, which must be updated manually when the hosts receives a release update.
Another customer (ID was already added to the list before) implemented a strategy to apply unattended upgrades and is looking for a way to upgrade UCS@School as well by using built-in methods on a considerable amount of systems.