Bug 34235 – UMC/UDM: init() seems to fail or not yet called

Bug 34235 - UMC/UDM: init() seems to fail or not yet called


Summary:	UMC/UDM: init() seems to fail or not yet called

Status:	RESOLVED DUPLICATE of bug 33848

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:	33627
Blocks:
	Show dependency tree / graph

Reported:	2014-03-04 10:16 CET by Florian Best
Modified:	2014-12-05 11:32 CET (History)
CC List:	4 users (show)

See Also:	33848 33627
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, External feedback
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Florian Best

2014-03-04 10:16:22 CET

We got another Traceback where the init() function of the UDM module hasn't been called.
This occurred before in the appcenter, so it looks like it is a generic UMC problem.

We will receive more information after UCS 3.2 errata 40 (→ Bug #33673 improved the behavior of failing init() methods).

3.2-0 errata0 (Borgfeld)
Traceback:
Die Ausführung des Kommandos udm/reports/query ist fehlgeschlagen:

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/univention/management/console/modules/__init__.py",
line 204, in execute
    func( request )
  File
"/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/__init__.py", line
487, in reports_query
    self.finished( request.id, self.reports_cfg.get_report_names( request.flavor ) )
AttributeError: 'Instance' object has no attribute 'reports_cfg'

+++ This bug was initially created as a clone of Bug #33627 +++

Comment 1 Dirk Wiesenthal

2014-03-04 11:18:58 CET

Maybe Bug#33848?

Comment 2 Florian Best

2014-03-05 09:23:34 CET

(In reply to Dirk Wiesenthal from comment #1)
> Maybe Bug#33848?
I was able to reproduce both tracebacks reliably:

When the ldap-server is down and one open any UDM module while no UDM module is currently running one will get (starting of UMC creates a UDM module process, it has to be killed manually):
AttributeError: 'Instance' object has no attribute 'reports_cfg'

If there is already a UDM module process running one will get:
LDAP_ConnectionError: Opening LDAP connection failed: {'desc': "Can't contact LDAP server"}

The reports_cfg error cannot occur anymore after errata 44 (Bug #33673).
Then the only thing we should do is to display a user friendly error message (→ Bug #34244).

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