Bug 33849

Summary:	DefaultPackagesMaster may block release updates on DC Master
Product:	UCS	Reporter:	Dirk Wiesenthal <wiesenthal>
Component:	UMC - App-Center	Assignee:	Dirk Wiesenthal <wiesenthal>
Status:	CLOSED DUPLICATE	QA Contact:	Florian Best <best>
Severity:	normal
Priority:	P5	CC:	best, gohmann
Version:	UCS 3.2
Target Milestone:	UCS 3.2-x
Hardware:	Other
OS:	Linux
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:

Description Dirk Wiesenthal

2014-01-06 12:15:23 CET

Slave installs app with DefaultPackagesMaster
->
Master registers component, installs the master package
->
App not marked as installed on master

If a new release of UCS is available this (somewhat "hidden") repository may block the update to the new version on the master, although the app is installed on the slave. The error message is irritating, a correct fix would be an update of the app on the slave system.

Note that this situation (DefaultPackagesMaster on a DC Master) may also lead to problems when there is a not backwards compatible cross update of UCS and the app (i.e. app_20140101 in UCS 3.1 ships a completely different schema package as app_20140101 in UCS 3.2). But this is unlikely to happen.

Comment 1 Stefan Gohmann

2014-01-14 12:28:24 CET

One way to solve this would be to remove DefaultPackagesMaster. Since UCS 3.2 the schema and other things could be registered via  ucs_registerLDAPExtension.

Comment 2 Dirk Wiesenthal

2014-01-31 11:30:56 CET

Should not happen anymore, now that MasterRepositories are removed after installation of DefaultMasterPackages

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

Comment 3 Florian Best

2014-02-10 17:39:47 CET

Ok, can not happen anymore.