Univention Bugzilla – Bug 43385
Installation succeeds with error messages if something was written to stderr
Last modified: 2017-02-22 12:33:01 CET
When some scripts write to stderr, this is shown as an error in UMC when installing an App. Sometimes the script does not fail, the stderr message was just a simple warning but everything was fine. This is highly confusing. We should only show errors when the installation actually failed.
We should also lower the log level in some cases, specifically when an ini file is not readable.
Ok, as discussed, i give this to you: Just changing the "log level" in the java code (remove res.level == 'WARNING' in AppDetailsPage.js@callInstaller) removes the stdout messages, but also in case of an actual failure. What we want is, no message on success=true, "all" message on success=false.
I have added some more test in 40_app_umc_install_latest_appbox (check installation if setup script writes to stderr but returns 0, check installation if setup script writes to stderr and returns 1). Please update install_via_umc in tests/80_docker/dockertest.py according to the fix here. Currently install_via_umc treats 'WARNING', 'ERROR', 'CRITICAL as errors.
Fixed in univention-appcenter 5.0.23-59.283.201702180315 by only using ERROR, CRITICAL, not WARNING. This means, to show an error, you have to do MODULE.error in UMC or self.fatal() or raise Abort() - self.warn() will not longer show up. I have raised and lowered some error messages. Also put that into ucs-test 6.0.37-53.1595.201702180320
OK - only critical errors are show OK - merged to 4.2-0 OK - test OK - yaml
<http://errata.software-univention.de/ucs/4.1/403.html>