Univention Bugzilla – Bug 42366
Capture information about joinscript failure in Feedback
Last modified: 2019-03-12 22:31:20 CET
Version: 4.1-3 errata239 (Vahr) Domäneneinrichtung (Dies kann einige Zeit dauern): FAILED: 35univention-management-console-module-diagnostic.inst We got no more information. We should add more information to the traceback reporting.
We should improve the quality of the errors which we report to the user. The error here is exactly what the user will see.
Ok, since we have no clue what's going on here, I think we should take this as an initiative to improve the collection of joinscript output. I guess that would require adjustment to umc-system-setup and/or supporting modules/libraries?
How do we handle this in the UMC join module? In the diagnostic module it's hard to identify the passage of the join.log that would be interesting for a specific joinscript execution failure. So maybe we should start dumping diagnostic output from the die() function into separate files for each failing joinscript? Evaluating and presenting that would be trivial. We could do this in two steps: if die() is called without arguments, then the it could save the join.log lines since "^RUNNING 90failedjoinscript". This first step would give us an immediate ROI for Support, and would also help the user when presented in UMC-diagnostic. The die() method could accept an argument (and options) where a joinscript can pass a different, more specific error output instead.
Failing joinscripts are reported every now and then. More information for the feedback-dialog would be really helpful. Version: 4.3-0 errata0 (Neustadt) FAILED: 26univention-samba.inst Version: 4.3-0 errata12 (Neustadt) FAILED: 96univention-samba4.inst Version: 4.3-0 errata0 (Neustadt) FAILED: 91univention-saml.inst Version: 4.3-0 errata21 (Neustadt) FAILED: 96univention-samba4.inst Version: 4.2-3 errata310 (Lesum) FAILED: 35univention-management-console-module-updater.inst
There are 3 different points where failing joinscripts get reported to the customer: -System Setup During system setup, all joinscripts get executed for the first time. If one fails the user gets presented with an error page with the possibility to report the error to us. This is where we get the traceback reports from that Florian and Johannes mentioned. -UMC Join Module When a join script fails in the join module, the user gets prompted with an error message that leads to the join log, which is conveniently available in the module itself. -Diagnostic Module The diagnostics module just runs univention-check-join-status and returns the output and links to an sdb article and the join module. As the bug originally was opened for improving the first case, I will focus on that for now. I don't think the join module needs any improvement for this as it already provides access to the log. The diagnostic module could get enhanced, but that probably is another bug.
Successful build Package: univention-system-setup Version: 11.0.5-4A~4.3.0.201806291616 Branch: ucs_4.3-0 Scope: errata4.3-1 Successful build Package: univention-join Version: 10.0.0-15A~4.3.0.201806291620 Branch: ucs_4.3-0 Scope: errata4.3-1 The relevant parts of the join log now gets added to the error message that appears in the system setup module after the join failed and gets sent to us if the user clicks the 'send feedback' button. I also made the logging a bit more consistent. Please test this on different system roles as the join process is vastly different. Also the python file sometimes isn't correctly loaded if you copy it onto the machine before the join. I tested it by writing 'false || die "teststring"' at the end (but before the line 'joinscript_save_current_version' of the joinscript '30univention-appcenter.inst'.
--- mirror/ftp/4.3/unmaintained/4.3-1/source/univention-system-setup_11.0.5-1A~4.3.0.201806081223.dsc +++ apt/ucs_4.3-0-errata4.3-1/source/univention-system-setup_11.0.5-4A~4.3.0.201806291616.dsc @@ -1,6 +1,18 @@ -11.0.5-1A~4.3.0.201806081223 [Fri, 08 Jun 2018 12:23:17 +0200] Univention builddaemon <buildd@univention.de>: +11.0.5-4A~4.3.0.201806291616 [Fri, 29 Jun 2018 16:16:29 +0200] Univention builddaemon <buildd@univention.de>: * UCS auto build. No patches were applied to the original source package + +11.0.5-4 [Fri, 29 Jun 2018 16:06:54 +0200] Jannik Ahlers <ahlers@univention.de>: + + * Bug #42366: Improve error message and feedback when join fails + +11.0.5-3 [Fri, 29 Jun 2018 15:10:42 +0200] Richard Ulmer <ulmer@univention.de>: + + * Bug #45931: Improve display of information about installed updates + +11.0.5-2 [Thu, 14 Jun 2018 13:17:43 +0200] Richard Ulmer <ulmer@univention.de>: + + * Bug #45931: Give more detailed information about installed updates 11.0.5-1 [Fri, 08 Jun 2018 12:01:09 +0200] Dirk Wiesenthal <wiesenthal@univention.de>: <http://10.200.17.11/4.3-1/#248385186724779815>
--- mirror/ftp/4.3/unmaintained/component/4.3-1-errata/source/univention-join_10.0.0-14A~4.3.0.201806212130.dsc +++ apt/ucs_4.3-0-errata4.3-1/source/univention-join_10.0.0-15A~4.3.0.201806291620.dsc @@ -1,6 +1,11 @@ -10.0.0-14A~4.3.0.201806212130 [Thu, 21 Jun 2018 21:30:25 +0200] Univention builddaemon <buildd@univention.de>: +10.0.0-15A~4.3.0.201806291620 [Fri, 29 Jun 2018 16:20:48 +0200] Univention builddaemon <buildd@univention.de>: * UCS auto build. No patches were applied to the original source package + +10.0.0-15 [Fri, 29 Jun 2018 16:10:01 +0200] Jannik Ahlers <ahlers@univention.de>: + + * Bug #42366: Repair logging of failed join scripts and adapt to changes in + system setup 10.0.0-14 [Thu, 21 Jun 2018 21:28:49 +0200] Arvid Requate <requate@univention.de>: <http://10.200.17.11/4.3-1/#248385186724779815>
Ok, this looks better. I created Bug 47327 to generally improve logging. For example if univention-join detects and error before running the join scripts, it outputs a single line prefixed with "* Message". For Bug 42124 I had to squeeze everything into this single line which is hardly readable in the System Setup output.
This breaks the installation tests! The setup process hangs in the "setup-scripts" status, seems that the execution of the join scripts in setup-join hangs forever with a read to stdin Next in setup-join is echo "Running postjoin scripts" but we can't see this in the setup.log, so the problem is in the if [ $? -ne 1 ]; then ... ( ... ) |& ( .. ) ... fi construct. Please make sure the installation tests are fine after fixing this.
Additional note to comment#10: we saw several tee processes lingering around while system setup was not progressing, it was showing the last executing joinscript in the progress bar. Killing the tee processes advanced the setup process
After killing 4 tee process, the setup continued, i applied the following patch - $i > >(tee -a "$JOIN_LOG") 2> >(tee -a "$JOIN_LOG" >&2) + $i 2>&1 | tee -a "$JOIN_LOG" and started the tests
17ab82392d | Improve readability of code 75a47d9bb2 | Advisory
Works very well. The joinscript output is parsed and shown to the user. Feedbackmails will be more helpful now. OK: univention-system-setup OK: univention-join OK: parsing of logfiles, correct detection of complete joinscript output. OK: Feedbackmails with error OK: yaml Verified
Whoops, clicked on verify to early. Commit b9dae7bd introduced a change to the die() function in management/univention-join/joinscripthelper.lib by explicitly setting "set +e". This will overwrite any modifications to that flag done by scripts calling that function. We should not change the flag in the function, or reset it to its previous state when exiting.
Ok, the "set +e" seems to have been a temporary setting during development of the patch. I've removed it and rebuilt the package: 7562556fb6 | Remove debug leftover c54386e7d2 | Advisory
OK: code review, set +e removed OK: yaml Verified
<http://errata.software-univention.de/ucs/4.3/214.html> <http://errata.software-univention.de/ucs/4.3/216.html>