Univention Bugzilla – Bug 32576
Apps installed many times in domain cause problems
Last modified: 2019-01-03 07:24:09 CET
Two problems in the following szenario: Master installs ucsschool-3.1rev0 -> component for ucsschool-3.1rev0 is registered on master and backup [time passes] Backup installs ucsschool-3.1rev1 -> component for ucsschool-3.1rev0 is unregistered on master and backup -> component for ucsschool-3.1rev1 is registered on master and backup -> PROBLEM 1: master thinks it has the latest and greatest version -> Next univention-update will install UCS@school Rev 1 [time passes] Backup upgrades to ucsschool-3.1rev2 -> component for ucsschool-3.1rev1 is unregistered on master and backup -> component for ucsschool-3.1rev2 is registered on master and backup -> PROBLEM 2: master will have a comlete UCS@school update. It is impossible to prevent this, even temporarily disabling ucsschool-3.1rev1 will not help
(In reply to Dirk Wiesenthal from comment #0) > Two problems in the following szenario: > > Master installs ucsschool-3.1rev0 > -> component for ucsschool-3.1rev0 is registered on master and backup > > [time passes] > > Backup installs ucsschool-3.1rev1 > -> component for ucsschool-3.1rev0 is unregistered on master and backup Why is the component unregistered on the master?
(In reply to Stefan Gohmann from comment #1) > Why is the component unregistered on the master? Because it is the "old" component and the code removes all old components when registering a new one. The problem would probably still be there if this un-registration would not happen. The new component is registered in any case and this makes the App Center think it has the newest version installed.
(In reply to Dirk Wiesenthal from comment #2) > Because it is the "old" component and the code removes all old components > when registering a new one. The problem would probably still be there if > this un-registration would not happen. The new component is registered in > any case and this makes the App Center think it has the newest version > installed. Sorry, for asking again. Which code removes the "old" component and why is the new component registered. In this UCS@school scenario we have no master packages in the ini file.
(In reply to Stefan Gohmann from comment #3) > In this UCS@school scenario we have no master packages in the ini file. I am very sorry. I saw this behaviour with another application but decided to take one from Univention as example. Replace ucsschool with another app that has MasterPackages (and more than one version throughout UCS 3.1 lifecycle), e.g. ucc.
(In reply to Dirk Wiesenthal from comment #4) > Replace ucsschool with another app that has MasterPackages (and more than > one version throughout UCS 3.1 lifecycle), e.g. ucc. Oh and maybe it should make sense to install this application on more than one server (just to have a realistic example). With all these requirements the szenario may be unlikely. Anyway it is still a bug. And if experienced, a serious one.
I see, as discussed via IRC we could add a warning when the app is upgraded "in background".
Should not happen anymore, now that MasterRepositories are removed after installation of DefaultMasterPackages *** This bug has been marked as a duplicate of bug 33947 ***
(In reply to Dirk Wiesenthal from comment #0) > Two problems in the following szenario: > > Master installs ucsschool-3.1rev0 > -> component for ucsschool-3.1rev0 is registered on master and backup > > [time passes] > > Backup installs ucsschool-3.1rev1 > -> component for ucsschool-3.1rev0 is unregistered on master and backup > -> component for ucsschool-3.1rev1 is registered on master and backup > -> PROBLEM 1: master thinks it has the latest and greatest version > -> Next univention-update will install UCS@school Rev 1 > > [time passes] OK → This is fixed > Backup upgrades to ucsschool-3.1rev2 > -> component for ucsschool-3.1rev1 is unregistered on master and backup > -> component for ucsschool-3.1rev2 is registered on master and backup > -> PROBLEM 2: master will have a comlete UCS@school update. It is > impossible to prevent this, even temporarily disabling ucsschool-3.1rev1 > will not help REOPEN → This still occurs
(In reply to Florian Best from comment #8) > > Backup upgrades to ucsschool-3.1rev2 > > -> component for ucsschool-3.1rev1 is unregistered on master and backup > > -> component for ucsschool-3.1rev2 is registered on master and backup > > -> PROBLEM 2: master will have a comlete UCS@school update. It is > > impossible to prevent this, even temporarily disabling ucsschool-3.1rev1 > > will not help > REOPEN → This still occurs hmm, the app is not updated anymore but all other packages (e.g. errata updates)
Okay. PROBLEM 1 was Duplicate of Bug 33947. But PROBLEM 2 still remains. The dist-upgrade when doing an update has nothing to do with "Master Repositories" now being removed.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.