Bug 33748

Summary: Improve traceback handling
Product: UCS Reporter: Dirk Wiesenthal <wiesenthal>
Component: UMC (Generic)Assignee: UMC maintainers <umc-maintainers>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P5 CC: best, gohmann, klaeser
Version: UCS 3.2   
Target Milestone: UCS 3.2-x   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=34995
https://forge.univention.org/bugzilla/show_bug.cgi?id=34244
https://forge.univention.org/bugzilla/show_bug.cgi?id=33963
https://forge.univention.org/bugzilla/show_bug.cgi?id=37366
What kind of report is it?: --- What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional): Error handling, Usability
Max CVSS v3 score:

Description Dirk Wiesenthal univentionstaff 2013-12-13 12:18:34 CET
In UCS 3.2 we introduced a traceback reporting tool.

Problem is that the tracebacks are not very meaningful. Sometimes they cannot: A meaningful traceback may expose confidential data, e.g. failed LDAP queries.

As tracebacks give really weak test experience, it might be useful to add another mechanism for selected code regions:
  A new UMC_Error that presents a dialogue to the user with a slightly improved layout:
  "The command %s failed. The following steps may help to solve the problem:
     * Updates are available. Install them first.
     * %s
     * %s
  If the error persists, hints about the cause can be found in the following log files:
     * %s
     * %s
  The following sections in the online documentation and the support database cover %s:
     * %s
     * %s
  If you have a maintenance contract with Univention, you can also contact the support, otherwise you may ask in the forum or send the traceback (along with the log files) to Univention."

Advantage: Feels better (we present solutions); does not look too technical and broken, more like "correct error handling" of a known issue.

Disadvantage: Hides the prominent "Send traceback" which may reduce feedback rate. Maybe a possible solution (e.g. a restart of the service) really works: We will never know of the initial problem (which may affect several more people).
Comment 1 Dirk Wiesenthal univentionstaff 2013-12-13 12:20:04 CET
Could be used in UVMM, we received a traceback:
File "/usr/lib/pymodules/python2.6/univention/management/console/modules/uvmm/uvmmd.py",
line 84, in request
    raise UVMM_Error(str(ex))

UVMM_Error: Could not open socket "/var/run/uvmm.socket": 2
Comment 2 Florian Best univentionstaff 2013-12-13 13:25:02 CET
If I had any free votes I would also vote for this bug.
Comment 3 Florian Best univentionstaff 2016-09-09 15:41:32 CEST

*** This bug has been marked as a duplicate of bug 38204 ***