Bug 39481 - uninstalling univention-demo-app removes univention-server-master
uninstalling univention-demo-app removes univention-server-master
Status: RESOLVED DUPLICATE of bug 39092
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-x
Assigned To: App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-06 14:26 CEST by Florian Best
Modified: 2016-02-23 13:58 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
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): Error handling
Max CVSS v3 score:


Attachments
management-console-module-appcenter.log (815.37 KB, text/plain)
2015-10-06 14:26 CEST, Florian Best
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2015-10-06 14:26:21 CEST
Created attachment 7203 [details]
management-console-module-appcenter.log

I removed the app 'univention-demo-app' via the appcenter. This removed the complete univention-server-master then.

I can't do anything anymore with slapd:
# invoke-rc.d slapd stop
sed: can't read /etc/ldap/slapd.d/cn=config.ldif: No such file or directory
invoke-rc.d: initscript slapd, action "stop" failed.
→ Can we harden the initscript?

It's not an easy reproducible case but the appcenter shouldn't do such things automatically.
We could add a blacklist of packages which must not be removed via appcenter.
I don't really know how that happend? Was univention-server-master flagged for autoremoval? If yes, what caused this? Can we detect states like when apt-get suggests 'install -f' like this is now the case due to broken slapd.

Bug #39325 also occurred as you can see in the logfile.
Comment 1 Florian Best univentionstaff 2016-02-23 13:58:13 CET

*** This bug has been marked as a duplicate of bug 39092 ***