Bug 54892 - univentionAppInstalledOnServer not cleaned if server will be removed
Summary: univentionAppInstalledOnServer not cleaned if server will be removed
Status: CLOSED FIXED
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Computers
Version: UCS 4.4
Hardware: Other Linux
: P3 normal
Target Milestone: UCS 5.2-2-errata
Assignee: Marius Meschter
QA Contact: Carlos García-Mauriño
URL: https://git.knut.univention.de/univen...
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-23 15:19 CEST by Dirk Schnick
Modified: 2025-08-20 15:28 CEST (History)
4 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?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.257
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2022062121000431
Bug group (optional):
Customer ID: 44145
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 Dirk Schnick univentionstaff 2022-06-23 15:19:31 CEST 
I have found removed servers in attribute univentionAppInstalledOnServer in a customer environment. From my point of view we should clean these attribute if we remove a server via UMC or udm. O have seen that on a 4.4 system but I'm sure this behavior is unchanged in UCS5.
I'm not sure if the component is correct. The procedure "remove a server" should be extended to remove all entries of that server in attributes univentionAppInstalledOnServer.

No big problem but noticeable.

Reproduce install f.e. samba4 on a server and remove that server via UMC. You will still find the server in the samba4 object in ldap in the attribute univentionAppInstalledOnServer
Comment 1 Lukas Zumvorde univentionstaff 2024-08-26 08:46:42 CEST 
I found the same issue at another customer. After removing a server and rejoining the Appcenter was effectively broken for that server, because of this issue. Since the LDAP data was still there for the APP it was still shown as installed and could not be installed. Since the container was not there it could not be upgraded or removed. Removing the entry from the LDAP solved the issue. However UDM is there to prevent such things from happening and without help the customer would not have been able to fix it.
Comment 3 Carlos García-Mauriño univentionstaff 2025-08-19 15:44:14 CEST 
Fixed in univention-directory-manager-modules (17.2.13)
Comment 4 Arvid Requate univentionstaff 2025-08-20 15:28:20 CEST 
<https://errata.software-univention.de/#/?erratum=5.2x173>