Bug 51578 – Starting a UCS release update via UMC does not install available errata updates before starting release update

Bug 51578 - Starting a UCS release update via UMC does not install available errata updates before starting release update


Summary:	Starting a UCS release update via UMC does not install available errata updat...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC - Software update
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 5.0-0-errata
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-06-25 12:22 CEST by Erik Damrose
Modified:	2021-04-28 10:19 CEST (History)
CC List:	3 users (show)

See Also:	51576
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.057
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erik Damrose

2020-06-25 12:22:27 CEST

When starting a release update via CLI with univention-upgrade, the order is to install available errata updates by default before starting the release update.

Starting a release update via the UMC updater module does directly start the release update by calling:
**** Starting univention-updater with parameter=['/usr/share/univention-updater/univention-updater', 'net', '--updateto', '4.4-5', '--ignoressh', '--ignoreterm']

Due to this behavior we cannot simply ship updates required to fix release problems as an errata update for the previous UCS version, because it may not be installed when the release update is started. Users are then required to install available errata updates, return to the updater module, and install the release update, which is not very intuitive.

This concerns e.g. a simple errata release for Bug #51576