Bug 57316 - The Appcenter should offer an option to specify if a "univention-app reinitialize" is supported
The Appcenter should offer an option to specify if a "univention-app reinitia...
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2024-05-23 09:14 CEST by Julia Bremer
Modified: 2024-05-23 17:25 CEST (History)
2 users (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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julia Bremer univentionstaff 2024-05-23 09:14:45 CEST
univention-app offers the command "reinitialize", which throws away the container  and starts a new one. 

With some apps this works well (I think e.g. nextcloud)
but with others (e.g Keycloak) this will result in a broken, not-starting container.

This results in support cases or even the support "breaking" a container by accident. 

Some apps depend heavily on their configure* scripts for the container to be functional. For example, Keycloak reads the LDAP for some of the Appsettings. This is done during the configure script. A "reinitialize" is done during the run of the configure script. Among other things


Currently it is not clear if that reinitialize works for that specific app or not.
I propose that the Appcenter should have some kind of option that doesn't allow a reinitialization. It should also make the error message configurable so that the App provider can enter what should be done instead. (E.g. in Keycloaks case: run univention-app configure).

Additionally, univention-app reinitialize will need a "force" flag so that it can be used internally even if the app doesn't really support it.
Comment 1 Jan-Luca Kiok univentionstaff 2024-05-23 09:24:54 CEST
I completely agree that this is a valid problem and something we should tackle, but to me this goes a bit too much into a solution proposal while the underlying issue might profit from something different.

For me the question would be: Why does this happen in the first place, so why is the command called? We should find a solution that solves this use case and also prevents app breakage on the way.
Was there a trigger for you to open the request, so someone I could talk to to understand the problem?