Bug 52934 - Docker container must have synchronized UCRV of the host
Docker container must have synchronized UCRV of the host
Status: NEW
Product: UCS@school
Classification: Unclassified
Component: HTTP-API (Kelvin)
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-03-17 11:00 CET by Dirk Schnick
Modified: 2021-05-11 15:47 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.171
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021031521000389
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Schnick univentionstaff 2021-03-17 11:00:02 CET
The last update of the Kelvin API causes a disfunctional import at the customer environment. The reason was, that the UCRV of the host are not in the container. Especially in the kelvin api app/container this problem will cause many support tickets the more the API will be used.

If we will dockerize more and more apps and services, we need a mechanism to synchronize our heart of configuration to these docker container.

There are already ideas and also a PoC created.
Comment 2 Dirk Ahrnke univentionstaff 2021-05-11 15:41:14 CEST
Another customer wanted to override the max length for the username which is set to 20 by default using UCRV ucsschool/username/max_length and tried to define it on the host. 
This did not work for obvious reasons. The definition of the UCRV inside the container will not survive the next update of the Kelvin-API unless there is a generic solution.
Comment 3 Erik Damrose univentionstaff 2021-05-11 15:47:34 CEST
To comment 2: Workaround is to write a custom hook script: https://docs.software-univention.de/manual-4.4.html#computers:Installation_and_Remove_hooks

The workaround does not reduce the importance of this bug report.