Univention Bugzilla – Bug 36822
Appcenter doesn't run joinscripts after installing e.g. univention-printserver to Memberserver
Last modified: 2015-03-11 15:09:56 CET
When using Appcenter on the DC Master to install e.g. univention-printserver on a Memberserver it doesn't execute the corresponding joinscripts. In this case it's pretty apparent from the fact that after the installation the Memerserver cannot be selected as the system hosting a new printer. The appcenter should probably ask for join credentials and run the remaining joinscripts on the target host.
(In reply to Arvid Requate from comment #0) > The appcenter should probably ask for join credentials and run the remaining > joinscripts on the target host. It should be the default to run the join scripts automatically. We can think about a checkbox which allows to skip the executing of the join scripts.
(In reply to Arvid Requate from comment #0) > [...] > The appcenter should probably ask for join credentials and run the remaining > joinscripts on the target host. It should be fine in 99% of all cases to use the credentials of the currently active user session.
*** Bug 36348 has been marked as a duplicate of this bug. ***
Fixed in: univention-management-console-module-appcenter 4.1.20-2.314.201502130101 Done by subprocess.Popen('univention-run-joinscripts'). Done even on DC Master (although joinscripts are probably called in postinst) to have a reliable environment. Joinscript output is sent to the progress bar by reading the last line of join.log. No new "area" in the progress bar is saved for this. univention-run-joinscripts is run at 100%.
OK: fix OK: installation/uninstallation OK: remote (un/)installation OK: wrong credentials / non-DomainAdministrator user ~OK: progressbar percentage (I tested the execution time of 6 join scripts, took about 1 minute, so it is OK). OK: YAML
http://errata.univention.de/ucs/4.0/96.html