Bug 49104 - Tracking code 200 sent even when the installation was not successful
Tracking code 200 sent even when the installation was not successful
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: UCS 4.4-0-errata
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-03-26 14:59 CET by Dirk Wiesenthal
Modified: 2019-03-26 15:00 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2019-03-26 14:59:22 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.
Comment 1 Dirk Wiesenthal univentionstaff 2019-03-26 15:00:04 CET
Maybe this explains some discrepancies in the Appliance reporting?