Bug 33484 – Release Update requires current App versions

Bug 33484 - Release Update requires current App versions


Summary:	Release Update requires current App versions

Status:	CLOSED FIXED

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

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.1-1-errata
Assigned To:	Dirk Wiesenthal
QA Contact:	Sönke Schwardt-Krummrich

URL:
Keywords:

Duplicates:	33564 (view as bug list)
Depends on:
Blocks:	33721
	Show dependency tree / graph

Reported:	2013-11-20 13:23 CET by Tim Petersen
Modified:	2013-12-12 11:30 CET (History)
CC List:	5 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
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 Tim Petersen

2013-11-20 13:23:57 CET

If not all App Center Apps are up to date the release update is blocked. The message within UMC should be improved.
At the moment it sais, that "the release update is blocked by component XY" - this implies "problems" with the component.

It should be pointed out that app center updates are needed before the release update.

We had several customer requests today regarding this message.

Comment 1 Moritz Muehlenhoff

2013-11-20 14:58:25 CET

We should fix this in an errata update soon, that is very confusing for users. 

The exact error message is:

Further release updates are available but cannot be installed because the component 'zarafa_20130228' is not available for newer release versions

That is very misleading, since the update _is_ available in the App Center, it only needs to be upgraded manually. This might even lead people into deinstalling the component to proceed.

I think the short term fix should be a different error message like

Further release updates are available but cannot be installed because the component 'zarafa_20130228' needs to be updated through the App Center.

In the mid term the online update should simply ask whether the compatible components should be upgraded along with the release update.

Comment 2 Stefan Gohmann

2013-11-20 16:40:21 CET

Should be fixed in the UMC module first.

Comment 3 Dirk Wiesenthal

2013-11-21 15:47:27 CET

Fixed in
  3.2-0 errata: univention-updater 9.0.38-2.1236.201311211352

YAML created.

No changelog, not built for next version

3.1-1 yet to be fixed

Comment 4 Dirk Wiesenthal

2013-11-22 14:43:50 CET

(In reply to Dirk Wiesenthal from comment #3)
> 3.1-1 yet to be fixed

3.1-1 built:
  univention-management-console-module-appcenter 2.0.139-22.215.201311211754
  univention-updater 8.0.78-8.1237.201311211757

slightly different because of missing function in 3.1 frontend

Comment 5 Alexander Kläser

2013-11-27 10:04:33 CET

*** Bug 33564 has been marked as a duplicate of this bug. ***

Comment 6 Sönke Schwardt-Krummrich

2013-11-27 17:03:08 CET

OK: source code change 3.1-1
OK: functionality 3.1-1
Note: components that are not part of the app center, may still cause the old 
      message (like 'oxmobility').
OK: package build/package version
OK: YAML

Comment 7 Janek Walkenhorst

2013-11-28 16:00:45 CET

http://errata.univention.de/ucs/3.1/195.html
http://errata.univention.de/ucs/3.1/196.html

Comment 8 Moritz Muehlenhoff

2013-12-12 11:30:29 CET

http://errata.univention.de/ucs/3.2/8.html