Bug 41496 – Must update local-repository after release update

Bug 41496 - Must update local-repository after release update


Summary:	Must update local-repository after release update

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Update - Repository administration
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	40338
Blocks:
	Show dependency tree / graph

Reported:	2016-06-08 18:14 CEST by Philipp Hahn
Modified:	2019-01-03 07:19 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
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.034
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016060821000567
Bug group (optional):	External feedback
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 Philipp Hahn

2016-06-08 18:14:17 CEST

A local repository server was updates to 4.1-2.
After that univention-repository-update was _not_ called.
This leads to
- 4.1-2-errata component missing afterwards
- 4.1-2-errata not being available to other hosts
- 4.1-2-errata not being included locally

This is probably a regression from Bug #40338

Ticket #2016060821000567

Comment 1 Stefan Gohmann

2019-01-03 07:19:43 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.