Bug 55527 – Local repository server - Special case PDC is also repository mirror for UCS 4.X

Bug 55527 - Local repository server - Special case PDC is also repository mirror for UCS 4.X


Summary:	Local repository server - Special case PDC is also repository mirror for UCS 4.X

Status:	NEW

Product:	UCS manual
Classification:	Unclassified
Component:	Release Notes
Version:	unspecified
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-01-03 13:31 CET by Lukas Zumvorde
Modified:	2023-01-04 11:15 CET (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a 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?:	Yes
School Customer affected?:	Yes
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 Lukas Zumvorde

2023-01-03 13:31:32 CET

A special case should be described in the release notes for repository mirrors.

If the Primary Directory Node also serves as a repository server for UCS 4.X, it is not sufficient to set the UCRV repositoy/online/server. Instead is is necessary to also set repository/mirror=no and local/repository=no. Otherwise the new repository can no be found. 


- Where is the documentation gap that needs a change needed? 
   https://docs.software-univention.de/release-notes-5.0-0-de.html#relnotes:localrepo
- What information did the documentation not deliver that you needed? What questions does the documentation not answer? What is missing?
   A description of the extra steps needed for the special case mentioned above.
- What is the impact of the documentation gap?
   The documented steps will no work in the special case.
- Who benefits from closing the documentation gap?
   UCS administrators of environments with local repository mirrors
- Why do you think should it be documented?
   To make the migration to UCS 5 easy for users with this special case.