Bug 39083 - Better error messages for UCS activation
Better error messages for UCS activation
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-05 10:52 CEST by Alexander Kramer
Modified: 2019-02-06 11:25 CET (History)
6 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016100621000268
Bug group (optional): Error handling, External feedback, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kramer univentionstaff 2015-08-05 10:52:00 CEST
+++ This bug was initially created as a clone of Bug #35614 +++

As discussed with Stefan this is a clone of Bug #35614
We still have to fix the following problems:

1) Provide a user friendly error msg thats helps the user to solve the problem
Currently the error handling inside 
* udm/__init__.py
* for the method _request_license(self, request):
provides unwanted error msgs for the following cases:

----
Case 1: License Server is not reachable

HOWTO: I added an entry into /etc/hosts like this:
-> 10.200.36.xxx <FQDN license Server>

behind the ip address is no server so you will get this error:
04.08.15 10:55:54.406  MODULE      ( ERROR   ) : ### str(exc): <urlopen error [Errno 113] No route to host>
04.08.15 10:55:54.406  MODULE      ( ERROR   ) : ### exc.reason: [Errno 113] No route to host
04.08.15 10:55:54.406  MODULE      ( ERROR   ) : ### exc.errno: 113
04.08.15 10:55:54.406  MODULE      ( PROCESS ) : An error occurred while contacting the license server: No route to host

----
Case 2: SSL Error

As discussed here:
http://forum.univention.de/viewtopic.php?t=3709&p=13298#p13298

I tried to reproduce the ssl error. Sadly I wasn't able to configure squid in such way that I got the same error. Instead I used a (miss)configured ip forwading to reproduce an ssl error. As you can see this will no be handled as expected. The msg that is provided to the user is still cryptic.

HOWTO: iptables -t nat -A OUTPUT -p tcp --dport 443 -j DNAT --to-destination :80


04.08.15 13:29:03.710  MODULE      ( ERROR   ) : ### str(exc): <urlopen error [Errno 8] _ssl.c:504: EOF occurred in violation of protocol>
04.08.15 13:29:03.710  MODULE      ( ERROR   ) : ### exc.reason: [Errno 8] _ssl.c:504: EOF occurred in violation of protocol
04.08.15 13:29:03.710  MODULE      ( ERROR   ) : ### exc.errno: 8
04.08.15 13:29:03.711  MODULE      ( PROCESS ) : An error occurred while contacting the license server: _ssl.c:504: EOF occurred in violation of protocol
-----

IMHO I think the problem is that we are evaluating exc.reason for the msg. I am not sure but I think that the reason won't provide a helpful msg for the user.

I would suggest I more generic msg if the known errors does not match.



2) Also currently this fix (Bug #38132) prevents the msg to be displayed (umc)

Inside
- univention-management-console-frontend/umc/app/ActivationDialog.js
- _evaluateActivation: function()
an error will allways display the same genric msg as an alert. Instead the response from the server have to be used.
Comment 1 Stefan Gohmann univentionstaff 2016-10-18 08:35:04 CEST
Once again. If UMC has no internet connection during the activation, one doesn't get feedback about it.

I re-tag the issue to a setup problem.
Comment 2 Stefan Gohmann univentionstaff 2016-10-18 08:36:17 CEST
(In reply to Stefan Gohmann from comment #1)
> Once again. If UMC has no internet connection during the activation, one
> doesn't get feedback about it.

Ticket #2016100621000268
Comment 3 Dirk Wiesenthal univentionstaff 2017-10-16 15:01:23 CEST
UCS Activation is not handled by the App Center anymore. Changing Component
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:20:35 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.