Univention Bugzilla – Bug 49104
Tracking code 200 sent even when the installation was not successful
Last modified: 2020-02-26 14:24:59 CET
When the installation routine raises an exception at a very early stage, the error handling is erroneous and the untouched default status of 200 is sent.
Happens when the LDAP server is down. The installation does not start, yet we think the installation was successful.
Maybe this explains some discrepancies in the Appliance reporting?
In actions/install_base.py some exceptions did not update the status code.
For those exceptions, a new error type "ResidualInstallationError" with the status code 502 was introduced.
The behavior can be tested by stopping the ldap server before installing an app.
The installation will now be acknowledged as failed.
Where did these changes happen, e.g. which commits in which git branch?
I can see there has been a rebuild of univention-appcenter in scope errata4.4-3, but no YAML for the package was commited. Please do that right after package build to ensure consistency and a stable errata release process
Sorry, my mistake.
Bug #49104: yaml
Bug #49104: added yaml
Bug #49104: Added ResidualInstallationError (statuscode: 502)
are now on branch 4.4-3
service slapd stop
univention-app install riot
send_information: action=install app=riot value=LDAP server is not running! status=502