Bug 49405 - Allow A Local Repository to Be Hosted on a Non-DC Server
Summary: Allow A Local Repository to Be Hosted on a Non-DC Server
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: General
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 48811
Blocks:
  Show dependency tree / graph
 
Reported: 2019-05-02 11:05 CEST by Christian Völker
Modified: 2024-06-27 12:09 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Feature Request
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):
Customer ID:
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 Christian Völker univentionstaff 2019-05-02 11:05:19 CEST 
In UMC when setting the policy for the repository server it is only allowed to select a computer out of the DCs as a repository server.

When setting the policy through udm we can set the value but it will stay empty whatever is configured:
root@master42:~# udm policies/repositoryserver create --position "cn=repository,cn=update,cn=policies,$(ucr get ldap/base)" --set name="ucs repository" --set repositoryServer="ucs.not-this-domain.de"


We should allow to set any server here instead of only UCS DCs.
Comment 1 Philipp Hahn univentionstaff 2019-05-02 11:17:22 CEST 
With Bug #48811 we introduce a new type of ComboBox, which allows specifying arbitrary values which are not in the default selection list.
Feel free to add "* affected" to that bug if applicable.
Comment 2 Jan-Luca Kiok univentionstaff 2024-06-27 12:09:52 CEST 
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.