Bug 48866 – S4-Connector: Avoid using logging.basicConfig

Bug 48866 - S4-Connector: Avoid using logging.basicConfig


Summary:	S4-Connector: Avoid using logging.basicConfig

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:	2019-03-05 18:00 CET by Dirk Wiesenthal
Modified:	2019-06-24 17:20 CEST (History)
CC List:	2 users (show)

See Also:
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):	Cleanup
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 Dirk Wiesenthal

2019-03-05 18:00:51 CET

Apparently, the S4 connector sets up logging by using basicConfig. While this is convenient for quick tests, it messes with all the fine tuned loggers and handlers that are used in other software of UCS.

More specifically, we had to workaround this twice in admin-diary. The diary client logged into the s4 connector log file although he was never meant to do that.

Other software cannot guarantee that its logging mechanisms suit the s4 connector.