Bug 33610 – Release policy not honored by UMC update module

Bug 33610 - Release policy not honored by UMC update module


Summary:	Release policy not honored by UMC update module

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Software update
Version:	UCS 4.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-11-28 15:01 CET by Philipp Hahn
Modified:	2019-01-03 07:22 CET (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary 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.046
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:

Flags:	best: Patch_Available+

Attachments
Hide releases > policy release (4.27 KB, patch) 2014-01-09 22:49 CET, Dirk Wiesenthal	Details \| Diff
View All 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 Philipp Hahn

2013-11-28 15:01:18 CET

UCS 3.1-1 errata194 system with UCS release-policy set to "3.1-1" and applied to the $ldap/base. The UMC still tells me that "3.2-0" is available and 

# /usr/share/univention-updater/univention-updater-check
...
Checking for release updates:                           found: UCS 3.2-0
...
# ucr get update/available
yes
# univention-policy-result -y /etc/machine.secret -D "$(ucr get ldap/hostdn)"{,}
...
Policy: cn=UCS-3.1,cn=update,cn=policies,XXX
Attribute: univentionUpdateVersion
Value: 3.1-1

Policy: cn=UCS-3.1,cn=update,cn=policies,XXX
Attribute: univentionUpdateActivate
Value: TRUE


May me related to Bug #33194 and Bug #33189

Comment 1 Alexander Kläser

2013-11-28 15:22:13 CET

Maybe related to Bug 29642?

Comment 2 Stefan Gohmann

2013-11-28 15:28:30 CET

(In reply to Philipp Hahn from comment #0)
> UCS 3.1-1 errata194 system with UCS release-policy set to "3.1-1" and
> applied to the $ldap/base. The UMC still tells me that "3.2-0" is available
> and 

Should the policy really be mandatory for the CLI and the UMC module?

Comment 3 Philipp Hahn

2013-11-28 15:44:54 CET

If I explicitly configure an UMC policy to update to at most 3.1-1 - in other words: I really really don't want 3.2 - I don't want to be nagged that there is a 3.2 release: I don't want to see that message first after login and I don't want anybody to update the system by accident.

Just my personal view worth ~2¢...

Comment 4 Dirk Wiesenthal

2014-01-09 22:49:58 CET

Created attachment 5726 [details]
Hide releases > policy release

Patch that hides newer releases on a relatively low level. I still have problems to build it with repo-ng, though

Comment 5 Stefan Gohmann

2014-01-10 06:10:23 CET

(In reply to Dirk Wiesenthal from comment #4)
> Created attachment 5726 [details]
> Hide releases > policy release
> 
> Patch that hides newer releases on a relatively low level. I still have
> problems to build it with repo-ng, though

See https://forge.univention.org/bugzilla/show_bug.cgi?id=33443#c5, I wrongly linked this bug. We should not change this behavior as erratum for 3.2-0.

Comment 6 Stefan Gohmann

2019-01-03 07:22:57 CET

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.