Bug 39268 – exceptions in UCR module handler aren't printed

Bug 39268 - exceptions in UCR module handler aren't printed


Summary:	exceptions in UCR module handler aren't printed

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	UCR
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Duplicates:	5303 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-26 15:49 CEST by Florian Best
Modified:	2020-07-29 17:09 CEST (History)
CC List:	3 users (show)

See Also:	38862 44966 51739
What kind of report is it?:	Development Internal
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
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

2015-08-26 15:49:07 CEST

If any exception occurs during a UCR module the only output is:
"""
E: your request could not be fulfilled
try `univention-config-registry --help` for more information
"""

IMHO the traceback or at least the exception should be printed.

Comment 1 Stefan Gohmann

2015-09-02 08:09:06 CEST

*** Bug 5303 has been marked as a duplicate of this bug. ***

Comment 2 Stefan Gohmann

2018-02-23 09:42:15 CET

Looks like --debug can be used:

Administrator@master431:~$ /usr/sbin/ucr set foo=bar
E: your request could not be fulfilled
try `univention-config-registry --help` for more information
Administrator@master431:~$ /usr/sbin/ucr --debug set foo=bar
Traceback (most recent call last):
  File "/usr/sbin/ucr", line 68, in <module>
    ub.main(convertToUtf8(sys.argv[1:]))
  File "/usr/lib/pymodules/python2.7/univention/config_registry/frontend.py", line 691, in main
    handler_func(args, cmd_opts)
  File "/usr/lib/pymodules/python2.7/univention/config_registry/frontend.py", line 127, in handler_set
    with ucr:
  File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 134, in __enter__
    self.lock()
  File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 121, in lock
    registry.lock()
  File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 399, in lock
    self.lock_file = open(self.lock_filename, "a+")
IOError: [Errno 13] Permission denied: '/etc/univention/base.conf.lock'
Administrator@master431:~$

Comment 3 Stefan Gohmann

2019-01-03 07:21:24 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.

Comment 4 Florian Best

2019-01-13 13:39:50 CET

Still relevant!

Comment 5 Philipp Hahn

2020-07-29 17:09:27 CEST

Bug #51739 war hard to debug because the TypeError was not printed.