Univention Bugzilla – Bug 39679
UCS components installed via apt-get are not registered immediately
Last modified: 2019-01-03 07:18:59 CET
Basically it works. I guesse there one glitch: Apps installed from the commandline are only shown after opening the App Center module the second time (in the same UMC session). E.g. login to UMC, open App Center, open shell and run "univention-install univention-fetchmail univention-fetchmail-schema", close App Center module, open it again: new App not shown. close App Center module again, open a second time: App is shown. This is even more irritating in the case where an umc-reload is triggered by the newly installed package. E.g. I installed univention-cups via univention-install and the UMC shows a popup "UMC reload required A reload of the Univention Management Console is required to use new modules. Currently opened modules may not work properly. Do you want to reload the page?", then I click Ok, the UMC reloads, but CUPS is not shown as an installed App. +++ This bug was initially created as a clone of Bug #39587 +++
I just ran into this and found another behavior: When the packages have been installed via cli and you open the app (which is shown as not installed), you can try to start the installation, which fails with the error "The app is already installed".
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.