Bug 54892 - univentionAppInstalledOnServer not cleaned if server will be removed
univentionAppInstalledOnServer not cleaned if server will be removed
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - Computers
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-06-23 15:19 CEST by Dirk Schnick
Modified: 2022-06-23 15:19 CEST (History)
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?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2022062121000431
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 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