Bug 32825 – after "univention-upgrade" UMC still shows "update available" message

Bug 32825 - after "univention-upgrade" UMC still shows "update available" message


Summary:	after "univention-upgrade" UMC still shows "update available" message

Status:	RESOLVED DUPLICATE of bug 31752

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

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-10-09 12:15 CEST by Ingo Steuwer
Modified:	2013-10-09 13:06 CEST (History)
CC List:	1 user (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):	Usability
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 Ingo Steuwer

2013-10-09 12:15:34 CEST

Reported by 2013092621001817

The customer installed the latest Errata-Updates on the commandline (univention-upgrade) and the UCR variable "update/availble" is set to "no", but UMC still shows an "updates are available" message after login. The message disappears after "/etc/init.d/univention-management-console-server restart" and "/etc/init.d/univention-management-console-web-server restart".

The expected behaviour would be that "update/available" is checked by each UMC login.

If updates are installed using the UMC module, the running UMC session forces a restart of the UMC services. I think for that reason the message disappears correctly then.

Comment 1 Alexander Kläser

2013-10-09 13:06:27 CEST

This behaviour has been corrected for UCS 3.2 (see Bug 31752). There, UCR variables are reload upon each UCR read request.

*** This bug has been marked as a duplicate of bug 31752 ***