Bug 33947 – Remove component for DefaultPackagesMaster after installation

Bug 33947 - Remove component for DefaultPackagesMaster after installation


Summary:	Remove component for DefaultPackagesMaster after installation

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	UMC - App-Center
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2-0-errata
Assigned To:	Dirk Wiesenthal
QA Contact:	Florian Best

URL:
Keywords:

Duplicates:	33849 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-01-17 14:47 CET by Dirk Wiesenthal
Modified:	2014-02-12 10:27 CET (History)
CC List:	2 users (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):
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 Wiesenthal

2014-01-17 14:47:32 CET

When installing an app with DefaultPackagesMaster, the DC Master adds the app's component and installs those packages.

The component remains in the list. Even when the app is uninstalled on the slave the master has the DefaultPackagesMaster installed (good, because schema extensions should remain) and the component activated (bad!).

This component can block releases (Bug #33849, Bug #33946) and even update an app when not requested (Bug #32576)

Components added just for the master packages should be removed after package installation. Those packages get orphaned but the alternative is far more unpleasant.

Check if the component is used complete installation before removing it!

Also add a script and run it to remove all those unnecessary components were added (before this fix) and not removed.

Comment 1 Dirk Wiesenthal

2014-01-31 11:28:49 CET

QA: Check bugs that are marked as a DUPLICATE of this bug.

Comment 2 Dirk Wiesenthal

2014-01-31 11:29:39 CET

*** Bug 32576 has been marked as a duplicate of this bug. ***

Comment 3 Dirk Wiesenthal

2014-01-31 11:30:56 CET

*** Bug 33849 has been marked as a duplicate of this bug. ***

Comment 4 Dirk Wiesenthal

2014-02-03 12:54:16 CET

Fixed in
  univention-management-console-module-appcenter 3.0.50-19.231.201402031215

Comment 5 Florian Best

2014-02-11 14:35:19 CET

On a freshly installed backup without any release updates the following message is printed often in the log:
( WARN    ) : Could not parse update.status: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/lib/univention-updater/univention-updater.status'
→ before scanning that file it should be checked if it exists

After installing owncloud5 on the overview site owncloud4 is displayed as installed.

Thanks for fixing this error:
tell_ldap() got an unexpected keyword argument 'log_ldap_error'

Comment 6 Dirk Wiesenthal

2014-02-11 15:19:28 CET

Fixed in
  univention-management-console-module-appcenter 3.0.50-21.233.201402111512

Comment 7 Florian Best

2014-02-11 16:10:24 CET

OK

Comment 8 Moritz Muehlenhoff

2014-02-12 10:27:17 CET

http://errata.univention.de/ucs/3.2/60.html