Bug 1080974 - import of ovirtfunctions cause stop log of ovirt-host-deply/otopi
Summary: import of ovirtfunctions cause stop log of ovirt-host-deply/otopi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.5.0
Assignee: Ryan Barry
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-26 12:17 UTC by Alon Bar-Lev
Modified: 2016-02-10 19:39 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 12:41:14 UTC
oVirt Team: Node
Embargoed:

Attachments (Terms of Use)
log-test.py (289 bytes, text/plain)
2014-03-26 19:02 UTC, Alon Bar-Lev 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 27270 0 master ABANDONED Don't break existing loggers when ovirt.node.log is imported Never

Description Alon Bar-Lev 2014-03-26 12:17:08 UTC 
Once:

        from ovirtnode import ovirtfunctions

The logging of otopi is halted.

For some reason this module modify the entire python logging or closes file descriptors.

The result is that we cannot see any log record past the point we persist files on ovirt-node.

This effects all ovirt-engine versions since 3.2.
Comment 1 Alon Bar-Lev 2014-03-26 19:02:17 UTC 
Created attachment 879174 [details]
log-test.py

reproduction script
Comment 2 Sandro Bonazzola 2014-05-08 13:50:37 UTC 
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed.
If this is a blocker please add it to the tracker Bug #1095370
Comment 3 Sandro Bonazzola 2014-06-11 07:04:37 UTC 
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
Comment 4 Sandro Bonazzola 2014-06-11 07:05:15 UTC 
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
Comment 5 Sandro Bonazzola 2014-10-17 12:41:14 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.