Bug 49541 - certificate check: Display proper error message instead on traceback when server can not be reached
certificate check: Display proper error message instead on traceback when ser...
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-05-24 09:37 CEST by Christian Völker
Modified: 2019-08-20 10:11 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a 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.046
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019030621000552
Bug group (optional):
Max CVSS v3 score:


Attachments
SCreenshot diagnose module (461.94 KB, image/png)
2019-05-24 09:37 CEST, Christian Völker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-05-24 09:37:57 CEST
Created attachment 10046 [details]
SCreenshot diagnose module

When the diagnose module checks certificates it tries to establish a connection to the target. IF this network connection fails for whatever reason a traceback is given. This traceback is displayed in UMC.

Tracebacks should never be seen by customers- we should have a proper error message here.
Comment 1 Florian Best univentionstaff 2019-05-24 10:05:10 CEST
Yes, I think instead of tracebacks the regular error handling should be done and a traceback-feedback-send dialog should be shown.
Comment 2 Christian Völker univentionstaff 2019-05-24 11:29:49 CEST
Well, a generic "unknown error - send feedback to Univention" might be better but in the end for the customer it is the same.

He will have no real idea what is going wrong.

I would prefer a proper error message like "Network connection has failed" or "Not able to contact target <HOSTNAME>".


When he gets an information about the possible root cause he will feel better informed and possibly can check on his own his environment. This improves trust into the product.... not giving useless error messages.

Just my thoughts.
Comment 3 Florian Best univentionstaff 2019-05-24 11:31:19 CEST
Of course, but this is only possible for your specific problem. Error handling for that case must be added, too.