Bug 53233 – rework "blocking components" in UMC updater

Bug 53233 - rework "blocking components" in UMC updater


Summary:	rework "blocking components" in UMC updater

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Update - Release updates
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-05-06 17:33 CEST by Felix Botner
Modified:	2021-05-06 17:33 CEST (History)
CC List:	0 users

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
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 Felix Botner

2021-05-06 17:33:29 CEST

Currently we have a mechanism to show blocking components for a release update.

When opening the UMC updater module on a system with such an component (that does not exist in the next release) a message is shown

"Further release updates are available but cannot be installed.
...
"

(1)
If this blocking component is a real updater component (repository/online/component/$COMPONENT/version=current), the "run_release_update" button is disabled. If the component is an app, the button is not disabled and the update can be started.

(2)
If there are patch-level updates before a minor/major update, there is no "blocking components" warning at all.

Let's say we are 4.4-7 and there are updates for 4.4-8 and 5.0-0. In this case no warning and ucs_version_text is pre-filled with 5.0-0 (the run_release_update is enabled of course)

This is all rather confusing.