Bug 48203 – univention-s4connector-list-rejected shows a traceback on hosts with deactivated S4 connector

Bug 48203 - univention-s4connector-list-rejected shows a traceback on hosts with deactivated S4 connector


Summary:	univention-s4connector-list-rejected shows a traceback on hosts with deactiva...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-11-26 14:19 CET by Christina Scheinig
Modified:	2021-05-14 16:46 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	4: Will affect most 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.183
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018112621000493, 2019012921000138
Bug group (optional):	Cleanup, 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 Christina Scheinig

2018-11-26 14:19:46 CET

The traceback shown on a backupserver within univention-s4connector-list-rejected, when the connector is not running, is a little bit confusing for a customer. We should display a message that the connector is not running on the backupserver if it is already running on a different server role.


root@backup:~# univention-s4connector-list-rejected 
Traceback (most recent call last):
  File "/usr/sbin/univention-s4connector-list-rejected", line 73, in <module>
    import mapping
ImportError: No module named mapping

Comment 1 Christian Völker

2019-01-29 17:33:46 CET

Customers executing the command on a backup server do not get proper information.



Instead of a traceback and a misleading error message we should state: "Should not be run when S4connector is not running on this host"